[MWForum]GraphicsBasics6

[Jeff Knope]

Hi Wendy,

Is it possible that MW 2.05 requires that the startup procedure be the very 
first procedure?  I seem to recall that some early LCSI Logos required that. 
When the change was made to no longer require it, I don't know.

I have placed the startup below the initially visible portion so as to be 
able to use the Procedures Tab for additional discussion and some simple 
examples.  It'd be nice to keep that feature, but if it's necessary the 
startup could be placed at the top.

I'm currently setting it up so there are a total of 10 different display 
options, permitting isolating most functions (some remain in pairs), 
offering various groupings, and uncluttering the screen.  There are buttons 
to select the desired option.

Wendy, I see you titled your message GraphicsBasics6. Does this mean you are 
now using GB6? If not, try it (it's attached to a 4/6 posting) to see if the 
problem you're having is still there.

It would sure be nice if SOMEBODY would tell us if they too have the problem 
you describe.

--Jeff



----- Original Message ----- 
From: "Wendy Petti" <wpetti@mathcats.com>
To: <mwforum@lists.mathcats.com>
Sent: Friday, April 08, 2005 6:21 AM
Subject: RE: [MWForum]GraphicsBasics6


> MicroWorlds 2.05 does indeed use startup procedures, so it is puzzling 
> that
> Mary is getting these error messages with MW 2.05.
>
> I would like to clarify that the difficulty I have been experiencing with
> the project is not in the setheading text box; it is when one activates 
> the
> auto-draw features, using coordinates.  The value in the setpos text box
> flickers constantly, even when the mouse is held steady, and if one
> activates the setx or sety text boxes, those flicker too.  If I click on 
> the
> blue ball to stop the auto-draw, the setx or sety text boxes continue to
> flicker; those processes are not stopped.  This happens for me in MW Pro.
>
> Jeff reports that nothing flickers when he runs the project in MW Pro (or
> EX).  We are both using Windows XP Service Pack 2.  We can't figure out 
> why
> we are having different experiences with the auto-draw text boxes.
>
> Jeff, you are asking why someone would want to use just the setheading
> feature... but I think part of the fun of MicroWorlds and of this forum is
> that we learn things by trying to adapt existing procedures in different
> ways.  However, removing a text box might have a ripple effect on other
> features.  Might I suggest instead, Jean, that you hide the text boxes and
> buttons that you don't want to see?
>
> Example:
>
> text1, hidetext
>
> set "button1 "visible? "false
>
> Wendy
>