Hi all,
Thanks to all for your suggestions.
I've found a solution to this question.
not sure if it is completely resolved, but seems to work quite well.
So, better share in the hope it will help few of you...
I've changed the filename of my stack, that's it !
then the name and the filename
Le 19 mai 2010 à 23:05, Malte Pfaff-Brill a écrit :
Thierry,
Hello Malte,
does your stack have any substacks that are still open?
Rev can not destroy it in that case.
Yes, one substack and sometimes it's visible, sometimes not visible.
Then, the mainstack is closed, but still in memory.
Thierry wrote:
Another point: this reminds me one thread on this list about someone
who couldn't start an external. I guess/feel that his problem could be
that
his stack was still in memory, and when he restarted it, the normal
process of
loading the external didn't work because the stack
Hi Thierry,
Yes, I am having the same problem. Once in a while, even after
explicitly deleting a stack with the delete command, the stack still
pops up somehow.
I think this is due to the compexity of the IDE. Probably, the IDE
team has used the long ID of a stack in several places,
Hi Thierry,
Yes, I am having the same problem.
Once in a while, even after explicitly deleting a stack with the delete
command,
the stack still pops up somehow.
Thanks Mark
I'm not alone ! Half the suffering is gone :)
I think this is due to the compexity of the IDE. Probably, the
Thierry D. wrote:
Hi all,
from time to time, in Rev IDE ( 4.0 MacOS ) when closing a stack,
the stack is still in memory, seen in the Application browser too.
DestroyStack and DestroyWindow are set properly !
and Yes, I refresh the application browser.
It had happened few times during my
Le 19 mai 2010 à 19:59, J. Landman Gay a écrit :
What happens if you type into the message box:
delete stack main stack
Does it go away then?
(Make sure you specify the mainstack, not the substack.)
Hmmm, as soon as I sent my email to this list,
it starts to work again :)
and
What happens if you type into the message box:
delete stack main stack
Does it go away then?
(Make sure you specify the mainstack, not the substack.)
Yes, it does!
However, if you have saved the stack
it will still exist where it has been saved.
All that DELETE STACK does is remove it
Richmond Mathewson wrote:
What happens if you type into the message box:
delete stack main stack
Does it go away then?
(Make sure you specify the mainstack, not the substack.)
Yes, it does!
However, if you have saved the stack
it will still exist where it has been saved.
All that
Been there as well, came to a little fix if you can call that a fix, instead
of closing the stack try something along the lines of:
delete stack myStack
This will really take it out of the memory, so these days, I close and then
I delete or vice versa...
On Wed, May 19, 2010 at 6:34 AM, Thierry
On 19/05/2010 22:19, J. Landman Gay wrote:
Richmond Mathewson wrote:
What happens if you type into the message box:
delete stack main stack
Does it go away then?
(Make sure you specify the mainstack, not the substack.)
Yes, it does!
However, if you have saved the stack
it will still
Le 19 mai 2010 à 21:38, Richmond Mathewson a écrit :
On 19/05/2010 22:19, J. Landman Gay wrote:
Richmond Mathewson wrote:
What happens if you type into the message box:
delete stack main stack
Does it go away then?
(Make sure you specify the mainstack, not the substack.)
Yes, it
Le 19 mai 2010 à 21:34, Andre Garzia a écrit :
Been there as well, came to a little fix if you can call that a fix, instead
of closing the stack try something along the lines of:
delete stack myStack
This will really take it out of the memory, so these days, I close and then
I delete or
Thierry,
does your stack have any substacks that are still open? Rev can not destroy it
in that case.
Do you reference to it with a filePath? - Will be reopened each time you
reference to it then.
Does it carry an external that is still used? - Rev won´t destroy it then AFAIK
Other than those
Malte Pfaff-Brill wrote:
Thierry,
does your stack have any substacks that are still open? Rev can not destroy it in that case.
Do you reference to it with a filePath? - Will be reopened each time you reference to it then.
Does it carry an external that is still used? - Rev won´t destroy it
4. Any open drivers must be closed
How to tell what are the open drivers? Is there a commad like
openStacks for drivers?
BTW, I too've suffered this destroystack wrong behavior, always
shrugging it off as something of my own doing rather than Rev's.
Something I'm even more convinced of after
16 matches
Mail list logo
