Hi All,
I need to get this working for a demo tomorrow and, as Murphys Law
Predicts, the one Stack I have the Save problem with is the one that
everyones will be looking at with a magnifying glass!
I tried everything I can think of to rid myself of this message
dialog. I have set destroyStack
Hi All,
I need to get this working for a demo tomorrow and, as Murphys Law
Predicts, the one Stack I have the Save problem with is the one that
everyones will be looking at with a magnifying glass!
I tried everything I can think of to rid myself of this message
dialog. I have set destroyStack
--- David Burgun [EMAIL PROTECTED] wrote:
Hi All,
I need to get this working for a demo tomorrow and,
as Murphys Law
Predicts, the one Stack I have the Save problem with
is the one that
everyones will be looking at with a magnifying
glass!
I tried everything I can think of to rid
Hi All,
I need to get this working for a demo tomorrow and, as Murphys Law
Predicts, the one Stack I have the Save problem with is the one
that everyones will be looking at with a magnifying glass!
I tried everything I can think of to rid myself of this message
dialog. I have set destroyStack
Hi Dave,
First of all : these Save dialog boxes will only
happen in the IDE ; so either demo a stand-alone app
or suspend the developmetn environment during the
demo.
Ok, but I'm having (different) problems with Standalone and just
wanted this to work 100% (or as close as possible!) in one
And saving the stack shortly before closing it (but not in the
closestack or closestackrequest) does not work?
Not sure what you mean by but not in the closestack or
closestackrequest. The stack scripts are as follows:
on preOpenStack
set the destroyStack of this stack to true
this is
Hi,
Ok more information on this!
In the Stack that brings up the Save Dialog, I have taken out the
preOpenStack handler (well dummied it, I now just have a beep in it),
so no Properties (or anything else) get set at all. The dialog still
appears when the Close Box is pressed.
I tried this:
Dave,
I have this very same problem. Here's what I do... When I get the Do you
want to save this Stack? dialog, I simply click Save and move on. It may
be a little annoying, but in my opinion, it's not worth spending over 12
hours on. Revolution is an amazing product! I certainly hope you
Hi,
Some more info. I did this:
From the IDE, saved the Stack.
From the Finder, duplicated the Stack.
From the IDE, Enter Browse Mode.
Called up the offending Stack via the MenuBar.
Hit the Close Window Button, get the save stack dialog, say yes.
From the IDE, Enter Pointer Mode.
Then using a
Hi David,
Dave,
I have this very same problem. Here's what I do... When I get the
Do you
want to save this Stack? dialog, I simply click Save and move on.
It may
be a little annoying, but in my opinion, it's not worth spending over
12
hours on. Revolution is an amazing product! I
--- David Burgun [EMAIL PROTECTED] wrote:
Hi Dave,
First of all : these Save dialog boxes will only
happen in the IDE ; so either demo a stand-alone
app
or suspend the developmetn environment during the
demo.
Ok, but I'm having (different) problems with
Standalone and just
wanted
Dave,
Your absolutely right - without question, RR should fix this issue. I guess
I'm more lenient about small issues like this. I get upset about the big
issues. Several years ago there was a bug in the toolTip property. If you
had a toolTip assigned to ANY object, the standalone would crash
David,
Sorry you're having so many problems.
Here's a couple things to you might try (if you haven't already):
1) Check the prefs - Files Memory. Click the radio button which says
Close the file
2) Just a thought, both stacks have different filenames, but do they
have different stack names?
Hi,
Your absolutely right - without question, RR should fix this issue. I guess
I'm more lenient about small issues like this.
Unfortunately, I (and more importantly the people that pay my salary
and buy licenses for tools like RunRev) don't see this as a small
issue! It has to do with
Hi Chipp,
Thanks for this, I changed the preference (was set to don't close)
but it made no difference.
Yes, the files have different Stack Names.
One other thing I noticed that is odd and it may have something to do
with what is going wrong.
When I have the Stack Window open in the IDE
Well I'd rather have an 'overactive' IDE that offers
to save every time I close a stack, then lose my work
because it didn't keep track well enough.
As Klaus noted, changing from browse mode to edit mode
is enough to trigger the IDE into 'edited' mode.
The problem is that it should 100% NOT save
David,
I have a plugin called AltClean which will removes the rev the
cREVGeneral custom property set from existing stacks. It might help
'reset' your stack (it won't harm it, but you should still always backup
your stack before using). You might wish to try it. It's at:
--- David Burgun [EMAIL PROTECTED] wrote:
Well I'd rather have an 'overactive' IDE that
offers
to save every time I close a stack, then lose my
work
because it didn't keep track well enough.
As Klaus noted, changing from browse mode to edit
mode
is enough to trigger the IDE into 'edited'
On 4/26/04 3:05 PM, David Burgun wrote:
I am not so worried that RR haven't fixed it, I am more worried that
having got the Stack file into a state that causes this to happen, that
no one seems to know what to do to undo it!
I suspect that some people aren't responding because they don't see it
I went digging through the IDE scripts, and found that
the global gREVStackSTatus isn' saved inside a custom
property or anything ; hence you must be doing
something that triggers the change to edited status
; in fact, it's enough to click in a field and not
even change anything, to chnge
Okay.. I'm definitely not the person to be trying to help but...
I remember ages ago some issue with breakpoints not clearing when Debug Mode
turned off and stacks crashing as a result after being opened (in earlier
versions). The fix was to clear breakpoints? on any stack that had
problems
Dave,
This is supposed to be a Professional software development package -
I don't think that ignoring a problem like this is in any way
professional.
How many other professional tools let you demo in the IDE? Maybe you
could let us know what standalone problems you are having, or run in
the
go to stack full-path/Stack1.rev
and in another place
go to stack full-path/Stack2.rev
Now, both Stack1.rev and Stack2.rev get displayed ok. They both have
close boxes. When I press the Close Box on Stack1.rev when running
from the IDE it displays the IDE Do you want to save this stack?
23 matches
Mail list logo
