Re: stack vs. exe behavior in altSplash deployment
Chipp Walters wrote: Hi Mark, see below for answers: On 11/26/06, Mark Powell <[EMAIL PROTECTED]> wrote: Anyway, a couple of questions -1- Cursor idiosynracies: Rev's built-in cursors aren't available (e.g. instead of hand and busy, I get the hourglass). How do I ensure that cursors port over correctly when a stack is deployed as a non-executable? I believe you can always embed a cursor in a stack and use it by setting the cursor ID to it. Perhaps Jacque can help out more here. Right, that's commonly used for custom cursors. You can do the same thing with the standard cursors, but then you can't refer to them by their named constants (i.e., "busy"). An easier way to embed standard cursors is to just tick the "Cursors" checkbox in the standalone settings dialog before building. Then they will work as expected. -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: stack vs. exe behavior in altSplash deployment
Hi Mark, see below for answers: On 11/26/06, Mark Powell <[EMAIL PROTECTED]> wrote: Anyway, a couple of questions -1- Cursor idiosynracies: Rev's built-in cursors aren't available (e.g. instead of hand and busy, I get the hourglass). How do I ensure that cursors port over correctly when a stack is deployed as a non-executable? I believe you can always embed a cursor in a stack and use it by setting the cursor ID to it. Perhaps Jacque can help out more here. -2- Saving state: When deployed as a non-executable, is it accurate to say that saving state (i.e. preferences, last state of checkbox, etc) is as straightforward as asking whether to save when the stack is closed? Certainly, that's one way. I prefer to separate my GUI/Business Logic with content and data..and in that end I prefer using small XML files to store prefs, and invisible stacks to store content-- I copy the content from the inv stack over to the Biz stack for editing, then close the stack. When I save, I generally create a new stack from scratch (or use a 'template stack') and write OVER the older stack. -3- Alpha channels: When used in the context of altSplash, is "alpha channel" synonymous with "transparency layer". I am getting transparency to work, but am wondering if I am not capitalizing on the effects available in the engine. Some PNG's have an 8 bit alpha channel. altSplash, built before alpha window effects came in 2.7+, faked it's own soft window effects. It still works in 2.7+. ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: stack vs. exe behavior in altSplash deployment
Hi Bill, altSplash is an unsupported splash screen architecture I provide for free. It works with the supported (and commercial) MagicCarpet, which is version control for files and works as a plugin within Rev. You can learn about altSplash at: http://www.altuit.com/webs/altuit2/MagicCarpetAAA/default.htm and MagicCarpet at: http://www.altuit.com/webs/altuit2/MagicCarpet/RevolutionPlugin.htm There is a much more advanced version of altSplash with new capabilities, but I don't have it fully documented yet. I'll hopefully get around to it soon and create a video tutorial on how to use it. BTW, Altuit currently uses altSplash to update and manage delivered code in virtually all of our projects. I imagine we've got 20 or 30 versions of it here at Altuit, and others, like Dan Shafer, use it as well. ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: stack vs. exe behavior in altSplash deployment
I've heard mention of altSplash a couple times... are you talking about the "butterfly" stack at http://www.altuit.com/webs/altuit2/RunRev/Downloads.htm or something else? A search on altuit.com on "altsplash" yields no results. Mark Powell" wrote: > [BTW Chipp: altSplash is to Rev apps what Dick Fosbury was to high > jumping--I hope you understand the compliment] ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
stack vs. exe behavior in altSplash deployment
I have an app in development that I am now transitioning to be "suitcased" with Altuit's altSplash architecture. [BTW Chipp: altSplash is to Rev apps what Dick Fosbury was to high jumping--I hope you understand the compliment] Anyway, a couple of questions -1- Cursor idiosynracies: Rev's built-in cursors aren't available (e.g. instead of hand and busy, I get the hourglass). How do I ensure that cursors port over correctly when a stack is deployed as a non-executable? -2- Saving state: When deployed as a non-executable, is it accurate to say that saving state (i.e. preferences, last state of checkbox, etc) is as straightforward as asking whether to save when the stack is closed? -3- Alpha channels: When used in the context of altSplash, is "alpha channel" synonymous with "transparency layer". I am getting transparency to work, but am wondering if I am not capitalizing on the effects available in the engine. Thanks very much Mark ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
