Monte-
Thursday, September 9, 2010, 8:34:11 PM, you wrote:
Did you know revTools comes back toplevel after it's hidden? I'm
sure it's fixed in the newer version
OK - that's a new one. I've never seen that, and none of the beta
testers have ever reported seeing it. Maybe there's some
I have a variation on this behaviour I've noticed.
My main stack inserts some front scripts from another stack. I
recent;y needed to debug a problem in one of the front scripts that
was called in the preOpenCard event of my main stack so set a
breakpoint in the fornt script, quit
Pete-
Thursday, September 9, 2010, 9:24:50 AM, you wrote:
I have a variation on this behaviour I've noticed.
My main stack inserts some front scripts from another stack. I
recent;y needed to debug a problem in one of the front scripts that
was called in the preOpenCard event of my main
I just call it from the message box. Its a bit manual but not oppressive.
Neal
On Thu, Sep 9, 2010 at 6:30 PM, Mark Wieder mwie...@ahsoftware.net wrote:
Pete-
Thursday, September 9, 2010, 9:24:50 AM, you wrote:
I have a variation on this behaviour I've noticed.
My main stack inserts
Neal-
Thursday, September 9, 2010, 5:08:26 PM, you wrote:
I just call it from the message box. Its a bit manual but not oppressive.
Ah, yes. The message box has its own special environment, and it can
trigger preOpenCard things because it's not trying to debug itself
while it's trying to open
On 9/9/10 5:30 PM, Mark Wieder wrote:
You can't debug preOpenXXX handlers with the builtin debugger.
I'm pretty sure I did, but with a printed breakpoint line instead of a
red dot in the side gutter. It's been a while though, maybe I'm
misremembering.
--
Jacqueline Landman Gay |
Jacque-
Thursday, September 9, 2010, 6:35:09 PM, you wrote:
On 9/9/10 5:30 PM, Mark Wieder wrote:
You can't debug preOpenXXX handlers with the builtin debugger.
I'm pretty sure I did, but with a printed breakpoint line instead of a
red dot in the side gutter. It's been a while though,
Hah! Fooled myself. I had previously put in a trap not to open the
debugger for testing. That'll learn me. Never mind.
--
-Mark Wieder
mwie...@ahsoftware.net
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to
Hi Mark
I can see a prefs xml file is created by PowerDebug. How do I get to the
preference settings? It would be handy if I got to them via the Plugins menu
but that's the execution error dialog and it hides itself immediately. Also is
it possible to turn off the tools palette hiding. I have
Monte-
Thursday, September 9, 2010, 7:23:06 PM, you wrote:
Hi Mark
I can see a prefs xml file is created by PowerDebug. How do I get
to the preference settings? It would be handy if I got to them via
the Plugins menu but that's the execution error dialog and it hides
itself immediately.
Yeah, I know.
Bringing it up from the plugins menu attempts to start the debugger
with no debug context, which just confuses everyone. You *can* bring
up the main page from the Application Browser and then click the help
icon from there, but that's kind of an ugly way to go about it as
well.
I have been using version 4.0 for about 2 months and find one thing
very annoying, that does not happen in version 3.5
When I set a breakpoint in the margin that appears as a red circle,
then run the handler, the breakpoint works as expected. If I make a
change in the code on a
On Sep 8, 2010, at 9:52 AM, Jim Ault wrote:
I have been using version 4.0 for about 2 months and find one thing
very annoying, that does not happen in version 3.5
It does happen in
4.03.5 on OSX 10.6.4Mac mini 2.4 Ghz Intel CoreDuo
4.0on OSX 10.5.8 G5 PPC
but not
I don't see this behavior at all, and I bet nobody else does. Wierd, but it
is something in your setup. This would be maddening, as you say.
Anyone?
Craig Newman
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to
Jim.
I guess I should have mentioned that the problem does not exist in OS
10.4.11. Rev v. 4.0 (build 950)
Craig
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
Hey! I was having that exact problem with GLX2 (which I still use and love
btw). I thought it was an incompatibility with Rev 4. Are you saying you never
used GLX2 and you are still having the problem?? My problem was at times
related to the fact that sometimes debug mode would turn itself off.
On Sep 8, 2010, at 1:54 PM, Bob Sneidar wrote:
Hey! I was having that exact problem with GLX2 (which I still use
and love btw). I thought it was an incompatibility with Rev 4. Are
you saying you never used GLX2 and you are still having the
problem?? My problem was at times related to the
Bob, Jim, et al-
Breakpoints are stored by the engine as a line number offset into a
script. If you edit the script after setting a breakpoint, it's up to
the script editor to adjust the breakpoints to accomodate the lines
added or deleted. Sometimes it works, sometimes it doesn't. GLX2 has
two
On Sep 8, 2010, at 2:14 PM, Mark Wieder wrote:
Bob, Jim, et al-
Breakpoints are stored by the engine as a line number offset into a
script. If you edit the script after setting a breakpoint, it's up to
the script editor to adjust the breakpoints to accomodate the lines
added or deleted.
On 9/8/10 4:10 PM, Jim Ault wrote:
Correct. Execution does not stop once I have added a character to the
code and compiled. Saving does not seem to have any effect.
I have not installed GLX2 or any other code editor or debugger.
My experience has been that editing anything under the
And thanks for sharing the results. We can all use this info.
On 8 September 2010 15:00, Jim Ault jimaultw...@yahoo.com wrote:
At least I now have a path to refurbishing old stacks to get back code
editing ease, if they need it.
This is a task for this very evening.
This is good...
It sounds like the token used in the compiled code for debug is getting
misplaced/ removed when an edit and recompile takes place.
Bob
On Sep 8, 2010, at 2:10 PM, Jim Ault wrote:
On Sep 8, 2010, at 1:54 PM, Bob Sneidar wrote:
Hey! I was having that exact problem with GLX2 (which I
Jacque-
Wednesday, September 8, 2010, 3:10:43 PM, you wrote:
My experience has been that editing anything under the breakpoint (lines
with higher numbers) works okay. Adding or removing lines above the
breakpoint (lower line numbers) causes problems. Changing something in a
line that
Fascinating. So how would I set a soft breakpoint as opposed to a hard one? I
use the breakpoint command. Is that the hard one? Which then is the soft
breakpoint used by GLX2?
Bob
On Sep 8, 2010, at 2:14 PM, Mark Wieder wrote:
Bob, Jim, et al-
Breakpoints are stored by the engine as a
Bob-
Wednesday, September 8, 2010, 3:23:17 PM, you wrote:
Fascinating. So how would I set a soft breakpoint as opposed to a
hard one? I use the breakpoint command. Is that the hard one? Which
then is the soft breakpoint used by GLX2?
Yes - the breakpoint command (or control-B )sets a hard
25 matches
Mail list logo
