Hi,
I'm bound to say, I'm in trouble with Dabo events.
I mean event raising order. I expected that developer events were
raised after framework events, but I was wrong.
Since framework events are responsible for specific control
behaviour I think that developer events should have lover priority.
Two examples (event listed in raising order):
1) dTextBox events are raised:
onKey (devel) - ForceCase and TextLength doesn't work
__onKeyChar (framework) - responsible for control properties behaviour
2) dPage events are raised:
onPageEnter (devel) - no items are available on first entry
__onPageEnter (framework) - call createItems() method.
Of course I can wrap my code into callAfterInterval() function,
but results can be unpredictable.
What if you change it a bit and instead of using:
for binding in self._EventBindings:
you change it to something like:
for binding in reversed(self._EventBindings) if
dabo.reverseEventOrder self._EventBindings:
?
--
Regards
Jacek Kałucki
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message: http://leafe.com/archives/byMID/[email protected]
