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
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
11 matches
Mail list logo
