Guild of Writers

To type š on a Mac you need to pull up the "Special Characters..." dialog.

As you might expect, I am biased towards "easy for beginners" on this question. Explaining the N different ways of typing accented characters (on Macs, Windows, Windows without keypad... iOS, Android, ...) seems like unnecessary pain.

(Having two different mappings available seems like unnecessary pain *on top of* the necessary pain. Inevitably people will try to copy from one to the other and get even more confused.)

belford wrote:To type š on a Mac you need to pull up the "Special Characters..." dialog.

As you might expect, I am biased towards "easy for beginners" on this question. Explaining the N different ways of typing accented characters (on Macs, Windows, Windows without keypad... iOS, Android, ...) seems like unnecessary pain.

(Having two different mappings available seems like unnecessary pain *on top of* the necessary pain. Inevitably people will try to copy from one to the other and get even more confused.)

Yeah, I meant to type that without having to use the dialog, which is pretty much can't be done with one keyboard layout.

The objection to it looking awkward in latin characters is pretty immaterial - it's not really intended to be rendered that way.

Course, the LM mapping need not be made known to everyone...

I do realise that this is unlikely to acutally go into Seltani, but variants of DniFont are one of my pet peeves.

Okay, thank you all for the discussion. I guess it's decision time.

zephjc wrote:Edit: I can copy-paste these numerals to the existing D'ni font so the original-style mixed-case input method can still be used.

This is what I'd like to go with. Would you? I'd appreciate it.

I've updated the property system, so that in-place modifications work. This means that all the usual ways of updating a list or dict should work correctly.

But there are a couple of corner cases:

- A world property (one defined by the creator) is immutable. If you define a value array in the build interface, and try to modify it in code, the changes won't stick.
- (However, if you assign a new array value in code, that becomes an instance property, which can be modified as expected.)
- If you modify a value so that it's equal to the old value, the change will not stick. For example, if you try this:
...the ls property will still be [0, 1, 2] afterwards. This is because the new value is equal to the old value, according to Python's rules: [0, 1, 2] == [0, 1.0, 2]. So the property system doesn't notice a change, so it doesn't write the new value back to the database.

If you notice any property bugs (other than this one :) please report them. This is a deep rewrite of the property-handling code, so it's possible that I screwed something up.

Is there a way to broadcast an eventloc() to multiple locations, but not the realm? for one of my Ages, I have the same message broadcast to 4 out of 6 locations, so I have to use 4 otherwise identical eventloc() functions, which I don't really like having to do.

You can do this:
Note that I'm using "_loc" as a temporary variable name -- the initial underscore makes it temporary. This means it won't get stored to the database, so the loop is slightly faster. (And doesn't wind up creating an instance "loc" property.)

You mean loops have been implemented now? Yay!

Tsani-Tsina has been updated.

I have finally got a lunar cycle working in Elahto! If all is working right, there'll be an eclipse tomorrow.