On 7/31/05 10:12 AM, Takehiko Abe didst favor us with:
> Laurence Harris wrote:
>
>> I can't think of anything super special I'm doing to get composited
>> windows to work with WNE.
>
> You moved a portion of your code from one place to another.
This makes no sense. There were changes needed to switch windows to
compositing, but they had nothing to do with WNE.
>
>> Would you care to describe specific incompatibilities, i.e.,
>> exactly what you think won't work in a WNE framework?
>>
>
> I do not think what won't work. You use HIView, right?
> Suppose you install event handlers that fetch every event and
> return noerr before HIView see them, would HIView still work?
> No. How do you make it work again? It's simple. You remove
> those event handlers. The compositing bit of window is just
> like that. I just turn it off and forget about it.
What are you talking about? This makes no sense at all. Sure, I can install
event handlers that make my windows stop working, but so what?
> I guess it is possible to "adapt the framework (david dunham)"
> by making it to use HIView and carbon-events -- but then, it
> won't be a WNE based framework anymore (which may be a good
> thing)
Not true. A WNE application is an application that uses WaitNextEvent
instead of RunApplicationEventLoop. Nothing more, nothing less. If what
you're meaning to say (but aren't) is that an application which relies
exclusively on handling EventRecords retrieved from WNE isn't fully
compatible with composited windows, then that's true, but really, who cares?
Relying solely on WNE event handling would be severely limiting, even if I
didn't have a single composited window in my application.
> and I have some reasons to believe that the framework
> will become less flexible. Also that means massive rewrite of
> both a framework and user codes.
You'd end up with a simpler framework in the end. The system now provides a
lot of functionality you used to have handle yourself.
> And the benefit? Other than
> the satisfaction that I am less behind from the Apples latest,
> I do not see much. It's "less attractive and beneficial to
> do so"
More and more features are only available to composited windows as time goes
on. Some of the newer interface elements can only be use in composited
windows, for example, and if IIRC, the HILayout stuff only works in
composited windows, which saves time in coding. Sure, if you want to cling
to writing applications that rely exclusively on EventRecords and never
write a CarbonEvent handler, you go right ahead.
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
