The point I want to make is that you shouldn't even ask this kind
of question. Instead of asking how to do some low level hack you
think you need to address something, you should ask for the best
way to address the higher level problem.
Larry has a point here... it may be useful to know what situation
you're in, what your constraints are. Why do you think you still have
to use DLOG and DITL resources for your windows? Did your app somehow
save them into its documents? DITL and DLOG are trivial formats ... a
DLOG is essentially a 2-byte-aligned struct that got saved to a
resource in PowerPC-endian format, and a DITL is an array of a couple
of shorts and longs plus a counter. You may save yourself a lot of
hassle by just writing a quick converter that outputs to, say, an XML-
plist format and then creating the appropriate controls yourself.
If this is just for the dialogs in your program, I'd suggest you
bite the bullet and just recreate your DLOGs and DITLs as NIB
windows. The Dialog manager is legacy technology, and kludging around
to modernize it simply is not worth the hassle, especially since all
the reasons people used to use it (in particular for legacy windows)
went away with the arrival of Appearance and more powerful controls.
-- M. Uli Kusterer
"The Witnesses of TeachText are everywhere..."
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden