Richard,
I think these problems are bugzilla'd originally in 4994 and then also
in 5362 (which is marked as a duplicate of 4994). However, the
workaround does not work for me.
On Nov 18, 2007, at 9:33 AM, Richard Gaskin wrote:
My first test was with the current shipping version, v2.8.1gm3. I
generally don't post about unreleased builds to a public forum.
I don't normally either. Sorry about doing it here.
But since you asked, I just reran the above test in v2.9b2, with the
same good result: the application contained no scripts and quit as
expected.
> Perhaps I can talk to you offline?
If we're going to put the time into this I'd rather it benefit
everyone. Can we just continue this diagnosis here?
I have worked with others on this and the simple fix listed in the bug
reports don't work so I don't think this forum would be conducive for
the diagnosis. However, I would be delighted to share whatever fix we
come up with.
The key difference here between working and non-working states seems
to be the presence of scripts which attempt to handle quit behaviors.
In your stack which is experiencing difficulty quitting, which
messages are you trapping and how are those messages handled?
That's the problem. If I am closing a window I successfully get
prompted for the save and if I say YES then everything works
correctly. However, if I say NO then it correctly doesn't save but
blocks subsequent trappings for other open stack windows.
Bill
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
