On 5/27/05 10:31 AM, Steve Mills didst favor us with:
> I'm sure lots of you have made the switch from WNE to RAEL. How did
> you proceed? Our framework handles all of the common events
> (activate, update, mouseDown, etc). Handling the activate event sets
> instance variables on the app object, like the current document. Our
> main event loop also handles deferred tasks after every event. These
> deferred tasks are deleting trashed objects, executing Apple Events
> that were created as the result of a drag, etc. This seems like it
> will be my biggest hurdle.
>
> All I've done so far to make the switch is to call RAEL and turned on
> the standard handlers and compositing flags on all windows we create.
My first thought is that both of these will almost certainly require that
you modify how you handle certain events. Have you adjusted your code for
these or did you just "turn them on?" If the latter, I'd go back to the way
you had it before, make one change at a time, get that working, and then add
another change. I'd start with adding the standard handler, then
compositing. Neither of these requires RAEL.
> Running the app after that change results in windows that barely
> update correctly, like for one app that puts up an empty document
> window when it launches that has a scroll list, a data browser, and
> some other minor controls, it will mostly draw, but a lot of things
> are drawn at the wrong origin. Then tabbing between the scroll list
> and data browser will draw the focused control and erase the other.
FWIW, I don't think your problems are related to using RAEL. It sounds more
like you switched to standard handlers and compositing without making the
necessary adjustments in your code.
Larry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
This email sent to email@hidden
