problems with debug terminal
Archiver
Posts: 46,084
Greetings,
I found a couple problems with the debug terminal (Ver 2.0 beta 1)
The first one is that my 'Debug Terminal #2' has no white 'transmit'
box at the top. I pushed the white box up and now can't get it to
come back down. (I know...it sounds like a personal problem [noparse];)[/noparse]
The 'pulldown' icon appears when you put the cursor over the top line
of the blue box but the white box does not pull back down.
Second problem is I cannot paste text (^C) into the transmit box on
any of the terminals. When I hit paste, it pastes into the
programming space that is behind the debug terminal. Not exactly what
I was trying to achieve. I have to send a 32 character line to the
stamp to test a serin parse function and dont wan't to type it each
time.
Any help on either problem would be appreciated.
Thanks,
Paul
I found a couple problems with the debug terminal (Ver 2.0 beta 1)
The first one is that my 'Debug Terminal #2' has no white 'transmit'
box at the top. I pushed the white box up and now can't get it to
come back down. (I know...it sounds like a personal problem [noparse];)[/noparse]
The 'pulldown' icon appears when you put the cursor over the top line
of the blue box but the white box does not pull back down.
Second problem is I cannot paste text (^C) into the transmit box on
any of the terminals. When I hit paste, it pastes into the
programming space that is behind the debug terminal. Not exactly what
I was trying to achieve. I have to send a 32 character line to the
stamp to test a serin parse function and dont wan't to type it each
time.
Any help on either problem would be appreciated.
Thanks,
Paul
Comments
> Greetings,
> I found a couple problems with the debug terminal (Ver 2.0 beta 1)
> The first one is that my 'Debug Terminal #2' has no white
> 'transmit' box at the top. I pushed the white box up and now can't
> get it to come back down. (I know...it sounds like a personal
> problem [noparse];)[/noparse]
Just as my doctor says when I tell him "It hurts when I do this",
don't do that! ;-) Actually, that sounds like a legitimate bug. I
just tried it myself, and it did the same thing. To fix it, I had to
edit the registry entry.
The registry key is HKEY_CURRENT_USER\Software\ParallaxInc\Stamp\1.32
\DebugXPos (where X is 1, 2, 3 or 4)
The value will be something like 0132,0090,0851,0614,0000,0000. You
can fix your debug terminal by setting the last value to something
like 0060. (At a minimum, it needs to be greater than zero.)
> Second problem is I cannot paste text (^C) into the transmit box
> on any of the terminals. When I hit paste, it pastes into the
> programming space that is behind the debug terminal. Not exactly
> what I was trying to achieve. I have to send a 32 character line to
> the stamp to test a serin parse function and dont wan't to type it
> each time.
This is the same problem that the Find/Replace dialog has. The work-
around is to right-click in the transmit box, and select "Paste" from
the pop-up context menu.
Good luck,
Greg Ross
Original Message
From: "gwrosss" <GWR@P...>
| The registry key is HKEY_CURRENT_USER\Software\ParallaxInc\Stamp\1.32
| \DebugXPos (where X is 1, 2, 3 or 4)
|
| The value will be something like 0132,0090,0851,0614,0000,0000. You
| can fix your debug terminal by setting the last value to something
| like 0060. (At a minimum, it needs to be greater than zero.)
Are you sure this works? I messed around with this and couldn't get it to
work. I tried all kinds of values from 0-100, and none of them seemed to fix
it. I re-started the program after each reg-edit, but I didn't reboot my
machine. I don't think a reboot is necessary, though, because options like
ToolbarVisible work fine...
- Robert
you do it or it reverts back when you close the program..I think)
Paul
--- In basicstamps@yahoogroups.com, "gwrosss" <GWR@P...> wrote:
> --- In basicstamps@yahoogroups.com, "Paul" <prcoy@y...> wrote:
> > Greetings,
> > I found a couple problems with the debug terminal (Ver 2.0 beta 1)
> > The first one is that my 'Debug Terminal #2' has no white
> > 'transmit' box at the top. I pushed the white box up and now
can't
> > get it to come back down. (I know...it sounds like a personal
> > problem [noparse];)[/noparse]
>
> Just as my doctor says when I tell him "It hurts when I do this",
> don't do that! ;-) Actually, that sounds like a legitimate bug. I
> just tried it myself, and it did the same thing. To fix it, I had
to
> edit the registry entry.
>
> The registry key is
HKEY_CURRENT_USER\Software\ParallaxInc\Stamp\1.32
> \DebugXPos (where X is 1, 2, 3 or 4)
>
> The value will be something like 0132,0090,0851,0614,0000,0000. You
> can fix your debug terminal by setting the last value to something
> like 0060. (At a minimum, it needs to be greater than zero.)
>
>
> > Second problem is I cannot paste text (^C) into the transmit box
> > on any of the terminals. When I hit paste, it pastes into the
> > programming space that is behind the debug terminal. Not exactly
> > what I was trying to achieve. I have to send a 32 character line
to
> > the stamp to test a serin parse function and dont wan't to type
it
> > each time.
>
> This is the same problem that the Find/Replace dialog has. The work-
> around is to right-click in the transmit box, and select "Paste"
from
> the pop-up context menu.
>
> Good luck,
> Greg Ross
*chuckles*
Paul
> Actually, that sounds like a legitimate bug. I
> > just tried it myself, and it did the same thing. To fix it, I had
> to
> > edit the registry entry.
> Thanks Greg, It worked. (but you can't have the program running
when
> you do it or it reverts back when you close the program..I think)
>
> Paul
I believe you're correct.
wrote:
>
>
Original Message
> From: "gwrosss" <GWR@P...>
>
> | The registry key is
HKEY_CURRENT_USER\Software\ParallaxInc\Stamp\1.32
> | \DebugXPos (where X is 1, 2, 3 or 4)
> |
> | The value will be something like 0132,0090,0851,0614,0000,0000.
You
> | can fix your debug terminal by setting the last value to something
> | like 0060. (At a minimum, it needs to be greater than zero.)
>
> Are you sure this works? I messed around with this and couldn't get
it to
> work. I tried all kinds of values from 0-100, and none of them
seemed to fix
> it. I re-started the program after each reg-edit, but I didn't
reboot my
> machine. I don't think a reboot is necessary, though, because
options like
> ToolbarVisible work fine...
>
> - Robert
As Paul discovered (and I didn't think to mention) you need to quit
the editor before making the registry changes.
Greg Ross
Original Message
From: "gwrosss" <GWR@P...>
| As Paul discovered (and I didn't think to mention) you need to quit
| the editor before making the registry changes.
Ooooopss... Duh!
I shoulda known better! [noparse]:o[/noparse])
- Robert