Bon Jurno, Paul,
Buon giorno, Rob,
1. Would this work?
Nice script. In my first post about this problem I have wrote that a
solution similar to yours may surely works, but I was searching for some way
to not load all images (for memory problemns) in my stack; now i'm supposing
that this will be
Bon Jurno, Paul,
You got reason, perhaps I have not explained well the problem. My stack is
an utility that simply shows the images of another choosen stack opened by
the user; so I cannot know if the user have one or many open stacks, and
what stack was opened before, or the potential ID
Dear Rob,
I cannot change in any way the X2 or X3 stack, because it is an external
stack, not mine, and it may change everytime: I'm not switching themes, I'm
browsing stacks.
on 5-01-2006 17:15, Rob Cozens at [EMAIL PROTECTED] wrote:
Can your design allow you to separate the images in X2
Paul,
Can your design allow you to separate the images in X2 from the
resources that must be opened?
I understand now that stacks X2 X3 were created by other people. I
also understand that, for whatever reason, X2 must be remain open
when X3 is opened.
This leaves me mystified as to
Hi Rob,
You got reason, perhaps I have not explained well the problem. My stack is
an utility that simply shows the images of another choosen stack opened by
the user; so I cannot know if the user have one or many open stacks, and
what stack was opened before, or the potential ID conflicts.
Hi Rob,
Very good work. It actually may help people who must switch themes of a
stack.
For my needs, I cannot close the stack X2, therefore your solution it's
not applicable.
Thanks however.
Paul Claude
on 5-01-2006 6:40, Rob Cozens at [EMAIL PROTECTED] wrote:
All,
Chameleon stack
Paul,
I cannot close the stack X2, therefore your solution it's
not applicable.
Can your design allow you to separate the images in X2 from the
resources that must be opened? (If not, why not?)
Keep what needs to be open in X2 and place the images in new stack,
X4. (There's no reason X2
Paul,
Can your design allow you to separate the images in X2 from the
resources that must be opened?
A simpler solution?:
on switchLibraries
stop using stack currentLibrary -- may need to be tweaked?
close stack currentLibrary
set the itemDelimiter to /
get item -1 of
if currentLibrary is imagePath2 then
stop using stack imagePath2
close stack imagePath2
lock messages -- [?]
open stack imagePath1 -- /or start using ?
unlock messages
-- don't change currentLibrary, so the next call will toggle
[may cause problems in line 1
Eric Chatonet
Images are the only objects the IDs of which can be changed:
Just change the IDs of some images to avoid any conflict :-)
And keep on hand the IDs list :-)
In order to be meticulous, you can store all images in a stack or a
substack, or put them onto a specific card dedicated
Hi Paul,
Well :-)
Sorry if I misunderstood.
You could try this tested workaround:
on SetImage pID
local tFlag
--
if there is an image ID pID then
set the ID of image ID pID to 25
put true into tFlag
end if
put image ID pID of stack X3 into image Template
-- or
I made things far too much complicated :-)
put image ID ID of stack x3 into image Image Name is enough ;-)
Best Regards from Paris,
Eric Chatonet
Le 4 janv. 06 à 14:04, Eric Chatonet a écrit :
Hi Paul,
Well :-)
Sorry if I misunderstood.
You could try this tested workaround:
on SetImage pID
Well :-)
Sorry if I misunderstood.
You could try this tested workaround:
on SetImage pID
local tFlag
--
if there is an image ID pID then
set the ID of image ID pID to 25
put true into tFlag
end if
put image ID pID of stack X3 into image Template
On 1/4/06 7:34 AM, Paul Claude [EMAIL PROTECTED] wrote:
Thanks, Eric, this surely works; I only was searching for a tip to avoid the
change (also if temporary) of the source image ID, as I can have many stacks
opened and many images to load together, but I am beginning to think that it
does
On 1/4/06 6:44 AM, Paul Claude [EMAIL PROTECTED] wrote:
P.S. Is there anybody that can tell me how to append my messages to this
list to an existing thread, without beginning each time a new thread (I use
entourage X)?
Well, I use Entourage 2004, and if you're talking about how to keep things
I made things far too much complicated :-)
put image ID ID of stack x3 into image Image Name is enough ;-)
Eric, the problem was another:
set the icon of btn x of stack X1 to (image ID ID of stack x3)
doesn't works if also in stack X2 there is an image with the same ID:
Revoultion loads
Then use the previous script a bit modified:
on SetImage pID,pButton,pStackName
local tFlag
--
set the cantAbort of this stack to true
if there is an image ID pID of stack pStackName then
set the ID of image ID pID of stack pStackName to 25
put true into tFlag
end if
Sorry: you will have rectified:
set the icon of btn pButton to 25
Le 4 janv. 06 à 14:51, Eric Chatonet a écrit :
Then use the previous script a bit modified:
on SetImage pID,pButton,pStackName
local tFlag
--
set the cantAbort of this stack to true
if there is an image ID
Paul,
Try:
start using stack x3
lock screen
repeat with x = 1 to the number of buttons
set the icon of button x to (the icon of button x)
end repeat
unlock screen
or going to another card in stack x1.
Well Rob, I really
Paul, et al,
If you care to send me your stacks privately, I will test it here.
Spurred on by Ken's assertion that it couldn't be done, I spent the
last 90 minutes trying to prove him wrong...and failed.
* I built a two card stack with three buttons with icons on the first
one button with
Paul, Ken, et al,
It's alive!
My icon-changing stack, Chameleon is now changing icons on-the-fly.
Chameleon stack script:
local imagePath1,imagePath2,currentLibrary
on openStack
get the effective fileName of this stack
set the itemDelimiter to /
put X2.rev into item -1 of it
put it
All,
Chameleon stack script:
On the vain presumption this might actually be of use to some people,
here's an improved version. Initialization is moved from openStack
to preOpenStack and the handlers otherwise tweaked.
local imagePath1,imagePath2,currentLibrary
on preOpenStack
get the
Hi, Paul,
Don't confuse the script of an object in the hierarchy with the order of
stack windows you ³see².
Invoking 'start using' places the *stack script* of that stack in the
*message* hierarchy, not the stack itself.
Construct a reference to a stack by name and that will be the
Hi Paul,
Images are the only objects the IDs of which can be changed:
Just change the IDs of some images to avoid any conflict :-)
And keep on hand the IDs list :-)
In order to be meticulous, you can store all images in a stack or a
substack, or put them onto a specific card dedicated to
Hi Paul,
3) 'Start using' or 'set defaultStack' does'nt change the things.
Try:
start using stack x3
lock screen
repeat with x = 1 to the number of buttons
set the icon of button x to (the icon of button x)
end repeat
unlock screen
or
Hi Paul,
There is a way to tell to Revolution to look in stack X before
the other
open stacks, even if they have been loaded previously?
start using stack X
places stack X ahead of all other library stacks in the message
chain; but it will not place it ahead of the topStack. The
Hi Paul,
start using stack X places stack X ahead of all other library
stacks in the message chain; but it will not place it ahead of the
topStack. The images may need to be on card 1 if the stack is in
use but otherwise unopened.
I am referencing images in the library stack as button
start using stack X places stack X ahead of all other library
stacks in the message chain; but it will not place it ahead of the
topStack. The images may need to be on card 1 if the stack is in
use but otherwise unopened.
Hi, Paul,
Don't confuse the script of an object in the hierarchy
To assign temporary an image to the button icon of your stack, Revolution
looks for the specified image first in the current stack, then in other open
stacks. But if you need to indicate an image of another open stack X
(without copying the image to your stack), you can assign this image to your
Hi Paul,
As far as I know: No.
Alphabetical order may be..
But the best way between different main stacks you want run together
is to not have the same IDs for any image.
Change them in the property palette.
But don't use the following:
* 1-100: reserved for built-in cursors
Eric,
isn't the Rev interop group reserving image IDs? Like passive
reserve, you just go there and reserve your range to make sure
there's no conflict when stacks are interoperating...
cheers
andre
On Dec 6, 2005, at 2:11 PM, Eric Chatonet wrote:
Hi Paul,
As far as I know: No.
Absolutely Andre :-)
Ken, [EMAIL PROTECTED] manages this with great kindness...
Le 6 déc. 05 à 17:15, Andre Garzia a écrit :
isn't the Rev interop group reserving image IDs? Like passive
reserve, you just go there and reserve your range to make sure
there's no conflict when stacks are
On 12/6/05 10:15 AM, Andre Garzia [EMAIL PROTECTED] wrote:
Eric,
isn't the Rev interop group reserving image IDs? Like passive
reserve, you just go there and reserve your range to make sure
there's no conflict when stacks are interoperating...
Yes, you can go to the RevInterop group on
On 12/6/05 10:18 AM, Eric Chatonet [EMAIL PROTECTED]
wrote:
Absolutely Andre :-)
Ken, [EMAIL PROTECTED] manages this with great kindness...
Thanks for this kind words, Eric! :-)
Ken Ray
Sons of Thunder Software
Web site: http://www.sonsothunder.com/
Email: [EMAIL PROTECTED]
Hi Paul,
There is a way to tell to Revolution to look in stack X before the other
open stacks, even if they have been loaded previously?
start using stack X
places stack X ahead of all other library stacks in the message
chain; but it will not place it ahead of the topStack. The
Paul, Eric, er al:
But don't use the following:
* 1-100: reserved for built-in cursors
* 101-135: reserved for built-in brush shapes
* 236-300: reserved for built-in patterns
* 301-1000: reserved for built-in icons
* 101,000-103,000: reserved
*
Hi Rob,
Interesting idea that could be mixed with profiles: not the easiest
to manage but...
:-)
Le 6 déc. 05 à 18:31, Rob Cozens a écrit :
I have suggested previously, but never seriously explored, the
possibility that one could change the look and feel of an app with
one start using
37 matches
Mail list logo
