m.schonewille at economy-x-talk.com
Fri Feb 27 03:19:21 CST 2009
Hi Jacuq and Craig,
Right, I see that too. The message box doesn't remember what the
current stack is and, worse, it doesn't remember when it needs to
refer to itself sometimes. This has several weird effects, one of them
being <http://quality.runrev.com/qacenter/show_bug.cgi?id=7743>. I can
very well imagine that Graig's problem has the same cause as bug 7743.
Economy-x-Talk Consulting and Software Engineering
Dutch forum: http://runrev.info/rrforum
Please visit <http://tinyurl.com/d6ojex> and click on "Stem" --Thank
On 27 feb 2009, at 07:28, J. Landman Gay wrote:
> dunbarx wrote:
>> I don't know, shooting a simple message like openCard right off of
>> its path is profoundly disturbing.
> In ten years I've never seen anything like that, and it seems like
> no one else has either. You're original. :)
>> Does anyone in Scotland know what that "/REVEXCLUDED02" is for?
> Probably, but they don't read this list routinely. What's going on
> shouldn't be happening though, so it's worth a bug report if you can
> create a small, reproducible example. The bug database is at <http://quality.runrev.com/
> > and any Rev user can enter reports there. That's the only way the
> team will see it.
> I have noticed a problem with the 3.0 message box lately myself, but
> it doesn't match your symptoms. What I've been seeing since the last
> release is the message box losing track of which stack it's supposed
> to point to. The name of the stack at the top of the message box is
> dimmed and commands sometimes go to the wrong stack, or go nowhere.
> Closing and re-opening the message box fixes it. It's a new bug and
> I'm watching for a reproducible recipe, but it seems to pop up on a
> There's a message watcher stack in the IDE, if you only want to
> track messages. That one works correctly and accomodates all the IDE
> busy-ness that goes on. The IDE is throwing hundreds of messages
> around behind our backs, you'll be amazed if you turn off all
> suppression and watch the message list for a while.
> Oh, and also, it's safer not to start any of your handler names with
> "rev" either, just like stack names. All the internal Rev messages
> start with "rev". It almost sounds like your script has a "rev"
> handler in it somewhere that could make the IDE think your
> backscript is a rev script. That'd throw a wrench in things if it
> happens. But a plain old "openstack" shouldn't be a problem. I'd
> look for other handler names that might conflict.
More information about the use-livecode