Re: image compression default

2006-11-29 Thread Richard Gaskin
Ken Ray wrote: So as Jan pointed out, the group is getting the startup message (since it's backgroundBehavior is true) and setting the paintCompression to png. Does it make any other changes to engine defaults beyond the paintCompression? -- Richard Gaskin Fourth World Media Corporation

Re: image compression default

2006-11-29 Thread Ken Ray
On 11/29/06 2:36 PM, Richard Gaskin [EMAIL PROTECTED] wrote: Ken Ray wrote: So as Jan pointed out, the group is getting the startup message (since it's backgroundBehavior is true) and setting the paintCompression to png. Does it make any other changes to engine defaults beyond the

Re: image compression default

2006-11-28 Thread Wilhelm Sanke
On Mon, 27 Nov 2006, Richard Gaskin wrote: Did we ever figure out how RunRev's revGeneral was able to alter the default image compression method when its script contains only handlers that must be explicitly called? -- Richard Gaskin Fourth World Media Corporation What kind of image

Re: image compression default

2006-11-28 Thread Richard Gaskin
Wilhelm Sanke wrote: The paintcompression default set by the engine is RLE, which is then overruled by the Rev IDE from stack revlibrary in folder toolset in the script of group revlibraries and its handler revLoadLibraries: on revLoadLibraries global gRevSmallAppIcon,gRevAppIcon local

Re: image compression default

2006-11-28 Thread Jan Schenkel
--- Richard Gaskin [EMAIL PROTECTED] wrote: Wilhelm Sanke wrote: The paintcompression default set by the engine is RLE, which is then overruled by the Rev IDE from stack revlibrary in folder toolset in the script of group revlibraries and its handler revLoadLibraries: on

Re: image compression default

2006-11-28 Thread Richard Gaskin
Jan Schenkel wrote: --- Richard Gaskin [EMAIL PROTECTED] wrote: That's exactly it: That handler isn't a native message -- what calls it? And once we find that culprit, it may be worth discovering what else it changes from natural engine behaviors. Doesn't the rev standalone builder add a

Re: image compression default

2006-11-28 Thread Wilhelm Sanke
Richard Gaskin [EMAIL PROTECTED] wrote: That's exactly it: That handler isn't a native message -- what calls it? And once we find that culprit, it may be worth discovering what else it changes from natural engine behaviors. The revlibrary stack is loaded together with the Rev IDE and

Re: image compression default

2006-11-28 Thread Richard Gaskin
Wilhelm Sanke wrote: The revlibrary stack is loaded together with the Rev IDE and then sends revloadlibraries from its preopenstack and preropencard handlers (which are located in group revlibraries) Besides other things and setting the paintcompression, revloadlibraries also inserts front and

Re: image compression default

2006-11-28 Thread Ken Ray
On 11/28/06 12:04 PM, Jan Schenkel [EMAIL PROTECTED] wrote: Doesn't the rev standalone builder add a background group to the first card of your mainstack? If my memory isn't playing tricks on me, then this bg group gets the 'startUp' message first, loads the 'revLibrary' stack so all the

image compression default

2006-11-27 Thread Richard Gaskin
Did we ever figure out how RunRev's revGeneral was able to alter the default image compression method when its script contains only handlers that must be explicitly called? -- Richard Gaskin Fourth World Media Corporation ___ [EMAIL