Re: [Whisper2-develop] Macros in whisper

[Jesse J. <jes...@mi...>]

At 3:11 AM -0400 8/24/03, Miro Jurisic wrote:
>>>    2 UNICODE
>>
>>This is defined by Microsoft's headers if you are building a 
>>Unicode version of your app. If this is the case all of the 
>>Window's API routines that take char*'s will want to take Unicode 
>>char*'s instead.
>
>Do we actually support using Whisper with UNICODE not defined?

Unless it has been changed, yes. Microsoft took a different approach 
than Apple to the problem of making their APIs Unicode savvy. As I 
mentioned when UNICODE is defined all of the routines that want 
char*'s automagically get changed to take UNICHAR*'s (or whatever MS 
used). What this means is that if you want a Unicode app you #define 
UNICODE and wind up with an app that won't run on anything but NT.

Of course this blows chunks. So, I took some care to write Whisper in 
such a way that you could have a fully Unicode savvy app on NT, but 
the binary would continue to run on Windows 98. This gets a little 
ugly in places, but the end result seemed to work pretty well. By 
defining UNICODE you can build an NT app and #ifdef out the 
work-arounds I had to add (although I don't think I ever tested this).

>>>    3 QUESA_SUPPORT_QUICKTIME        // huh?
>>
>>This is mostly for Windows where you might want to build a Quesa 
>>app without requiring that QuickTime be installed.
>
>Would its definition come from Quesa SDK? I don't see a definition, 
>only use, in ours.

I think it's a Whisper define.

   -- Jesse