on textoid txt
lock messages
create stack
set name of the topstack to Textoid
go to card 1 of stack textoid
-- why is the previous line necessary? go figure...
create field
set the rect of fld 1 to the rect of card 1
put txt into fld 1
end textoid
then type in the message something
Actually i got the same behavior after a couple runs from the clean
installed MC stack.
I tried in vain to put a breakpoint but that command doesn't work for
nothing.
Anyone has any idea?
Im really lost... and nothing in the debugging section seems to work in this
case.
There is no error in
The reason you get the strange behavior is the go to card 1 of stack
textoid line. The first time I ran your code, I got one window that
looked right. Then I closed the window and ran it again, and experienced the
behavior you identified.
What's happening is that when you close a stack
[EMAIL PROTECTED] wrote:
on textoid txt
lock messages
create stack
set name of the topstack to Textoid
go to card 1 of stack textoid
-- why is the previous line necessary? go figure...
create field
set the rect of fld 1 to the rect of card 1
put txt into fld 1
end textoid
Okay, here's my problem, maybe someone can see a problem with my logic:
I have a handler (loadFonts) that makes a list of the user's fonts,
sorts it alphabetically, and puts it into a button in the stack's
menuGroup (titled, appropriately enough, Text ) .
However, I keep getting an execution
- Original Message -
From: Karl Becker [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, May 03, 2001 4:07 PM
Subject: Strange behavior (2.3.2)
Okay, here's my problem, maybe someone can see a problem with my
logic:
I have a handler (loadFonts) that makes a list of the user's
