I am sorry, Adam, to take such a time . . .
however you can download a 'full-on' demonstration of
Window-Positioning (TL.rev.zip) at the new Yahoo Group I
have set up for discussing graphic-related topics in
connexion with RR:
http://groups.yahoo.com/group/RRgraphix/
sincerely
Perhaps I should have mentioned that I tend to use
'lockScreen' while I am moving stacks round people's
monitors
as it can look a bit odd that when they start something up
the first thing it does is slide from somewhere into the
middle!
on openStack
set the lockScreen to true
put item 3 of t
Pop the following into your stack script:
On openStack
put item 3 of the screenRect into WID
put item 4 of the screenRect into HITE
move stack "BLAHBLAH" to (WID / 2),(HITE / 2)
end openStack
where "BLAHBLAH" is the name of your stack
Love, Richmond
___
Hi Adam,
in the stack script of the mainStack
on preOpenStack
set the loc of this stack to the screenloc
end preOpenStack
then make sure and pass the preOpenStack message (if you're trapping it)
from your other stacks.
best,
Chipp
Adam wrote:
Hi All:
I'm loving the fact that my first
Hi All:
I'm loving the fact that my first Rev is now working as it should, but
now comes the cosmetic bits... is there some way to make sure that when
my application is running the program itself is in the centre of the
user's desktop, as well as making sure that any substacks open in the
ce
Le 13 juil. 05 à 15:23, Eric Chatonet a écrit :
revApplicationOverview and revDocs
Le 13 juil. 05 à 15:19, Jim Bufalini a écrit :
Now I suppose, if somebody knows the names of the Application
Browser and
Reference Documentation stacks, you could use your Message Box to
set their
Locatio
Alt-space... Well, that makes the second new thing I learned today! :-)
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 13, 2005 3:23 AM
To: [EMAIL PROTECTED]; How to use Revolution
Subject: RE: Window Positioning Bug? [WORKAROUND
lication Browser and
>Reference Documentation stacks, you could use your Message Box to set
their
>Locations back to your main monitor. Anyone?
>
>Jim
>-Original Message-
>From: Charles Hartman [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, July 13, 2005 2:06 AM
>To: [EMA
revApplicationOverview and revDocs
Le 13 juil. 05 à 15:19, Jim Bufalini a écrit :
Now I suppose, if somebody knows the names of the Application
Browser and
Reference Documentation stacks, you could use your Message Box to
set their
Locations back to your main monitor. Anyone?
Best Regard
yone?
Jim
-Original Message-
From: Charles Hartman [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 13, 2005 2:06 AM
To: [EMAIL PROTECTED]; How to use Revolution
Subject: Re: Window Positioning Bug? [WORKAROUND]
On Jul 13, 2005, at 7:40 AM, Jim Bufalini wrote:
This raises a secon
Eric,
> If you set the bottomRight of a window to negative values (or at least
"0,0"),
> this should never happen :-)
I just tested this, and this is incorrect. If you *place* your second
monitor at -1024, -768 (which, in my case, would be diagonally upper left of
the main monitor) and set the bo
On Jul 13, 2005, at 7:40 AM, Jim Bufalini wrote:
This raises a second question, though. I run two monitors. How does
Rev
address the second or more monitors (I believe the limit software
wise in
WinXP is 9 monitors)? I notice, for example that the Documentation
screen
reliably comes back,
Hi Jim,
If you set the bottomRight of a window to negative values (or at
least "0,0"), this should never happen :-)
Le 13 juil. 05 à 13:40, Jim Bufalini a écrit :
I guess these two questions are related, so that when putting
something
*offscreen* you don't accidently put it on someone else
Scott,
>Thanks Chipp. However the issue I'm trying to address is to reliably place
>a stack offscreen, which is used in any number of routines (not just my
>import script).
Ah-ha! Is this how to get around that picture flash that occurs during
*import*? I've tried lock screen, setting defaultSta
>> When I run the following script, I actually see the offscreen-intended
>> window appear every *other* time, in other words a reliable failure that
>> occurs 50% of the time:
>>
>> on showWindow
>> set topLeft of stack progind to 1,1
>> palette stack progind
>> put windowID of stac
Hey man,
couple things you should consider trying.
1) check the windowBoundingRect and set it larger.
2) set the stack's formatForPrinting property to true, this will ignore
the windowBoundingRect; be aware of editing any text of a stack who's
formatForPrinting prop is true.
3) Don't use a pal
set to negative
numbers.
I've noticed this failure in other stacks but wasn't sure if this
was a
result of my code. Now it seems very repeatable, and I believe
other folks
have mentioned window positioning problems as well.
Can anyone else verify this? Is this a coding problem
this was a
result of my code. Now it seems very repeatable, and I believe other folks
have mentioned window positioning problems as well.
Can anyone else verify this? Is this a coding problem or bug?
Thanks & Regards,
Scott Rossi
Creative Director
Tactile Media, Multimedia & Design
-
E: [
Thank you Sarah this has the desired affect.
N
-Original Message-
From: Sarah [mailto:[EMAIL PROTECTED]]
Sent: 28-Jan-03 9:20 PM
To: [EMAIL PROTECTED]
Subject: Re: Stack window positioning.
I don't know what this would look like but you could try:
lock screen
go invisible to
I want to open two different cards within two separate stacks.
However, I want the card in the first stack window to remain underneatch the
second stack that I open.
I used:
go to stack "FirstStack"
go to stack "SecondStack"
but I see the first stack when it opens. I have tried:
go invisible t
20 matches
Mail list logo
