The real Challenge for every development platform
b.xavier at internet.lu
Sun Jan 23 12:51:05 EST 2005
It's better to have a confusing cursor than a confusing language!
The events can have some exceptions but it's usually solid!
Since day 1 I notified the cursor horror but no one cared
at the end... But no one is stopping you from using your own!
for your startup stack script...
set cursor to mycursor
> -----Original Message-----
> From: use-revolution-bounces at lists.runrev.com
> [mailto:use-revolution-bounces at lists.runrev.com] On Behalf Of
> Marty Billingsley
> Sent: Sunday, January 23, 2005 18:26
> To: use-revolution at lists.runrev.com
> Subject: Re: The real Challenge for every development platform
> > Judy Perry <jperryl at ecs.fullerton.edu> writes:
> > Another newbie issue -- the cursor. Those two selection cursors
> > simply look waayyy too similar, the operative distinction
> between the
> > two is not visually intuitive, and, as someone here noted,
> you often
> > have to look long and hard to see which one you're using at
> any given
> > time (leading to the sort of modal errors that could entirely
> > frustrate if not directly turn away a newcomer).
> Can anyone explain *why* Rev decided to have the edit cursor
> and the run cursor look the same? It makes it extremely
> difficult for my students to keep in mind which mode they are
> in (develop vs. test).
> It's also *really* confusing for them when some messages are
> passed to controls in edit mode and some are not. For
> example, mouseUp isn't passed to a button when you click on
> it in edit mode, but mouseEnter is passed to the button when
> you mouse over it. Very confusing.
> Anyone got a clear explanation why this is desirable? (I've
> been telling my students that it's a bug in the way the
> software is written, but perhaps it's really a feature....)
> - marty
> Marty Billingsley
> The University of Chicago Laboratory Schools
> use-revolution mailing list
> use-revolution at lists.runrev.com
More information about the Use-livecode