AWAR handling in gtk breaks application behavior

[westram]

Examples are hard to detect (one example of changed behavior is provided by #600).

gtk-version somehow changes order of awar-callbacks (compared with motif version). This is especially true when awar-update-callbacks change other awars.

Some facts about awar-updates:

• awars located in the properties do call their update-callback instantly (because the properties is transaction freee)
• awars located in the main arb , call their update-callback at the end of the current transaction. Depending on the context, this transaction may either be some -transaction or the transaction started by the awar-update itself or some transaction started by the update of another awar (which interacts with the current awar by setting the value of the current awar in the change-callback of the other awar).
• I've tried to change the transaction mode of the property- in the past, but this massively changes the behavior of arb and need intense testing/fixes.

Bugs arising from the changed update-behavior may occur anywhere in the arb interface where multiple awars are interconnected via their change-callbacks.

[westram]

gtk-port is dead

[westram]

Ticket retargeted after milestone deleted