How about an updateText() function added to the label widget that
would call setText().
--
// Robert Rainwater
On 12/10/2000, 5:18:11 PM EST, Scott wrote about "[Dynapi-Dev] Label text selection":
> Yeah, that's something I overlooked. setText needs to be called in order to
> see an immediate change, but there's no reason to call setText every time
> you change a label property. Doesn't setHTML also fire a load event, too?
> An addition boolean passed to each of the setter method could determine if
> the text is to be re-rendered. or optionally, we could just require that
> setText should be invoked manually, rather than automatically from within
> another setter method.
> ------
> scott andrew lepera
> [EMAIL PROTECTED]
> web stuff: www.scottandrew.com
> music stuff: www.walkingbirds.com
> -----Original Message-----
> From: Robert Rainwater <[EMAIL PROTECTED]>
> To: DynAPI Development List <[EMAIL PROTECTED]>
> Date: Friday, December 08, 2000 9:05 PM
> Subject: Re: [Dynapi-Dev] Label text selection
>>
>>Another problem witht the list/label widgets is the many calls to
>>setText. In ListItem, the onmouseout and mousemouse over makes to
>>different calls to change the font (forecolor, textcolor). Each one
>>of these calls, calls setText which sets the html.
>>
>>Maybe we should pass a boolean to the font change functions, that
>>decides whether or not to call setText.
>>
>>--
>>// Robert Rainwater
>>
>>On 12/8/2000, 6:37:49 PM EST, Scott wrote about "[Dynapi-Dev] Label text
> selection":
>>
>>> There's a small snag in Label. In IE, when you use setSelectable to
>>> prevent text from being selected with the mouse, you're also cancelling
>>> the browser event. This can also cancel events on the label itself.
>>> For example, if you build a list item out of a label with rollover color
>>> change events, sometimes the label text will cancel the onmouseout
>>> event. If you mouseover the list fast enough you may end up with
>>> several items stuck in the rollover position. This could cause problems
>>> with other widgets that use Label.
>>
>>> In light of this, I'm wondering if we should restore the optional
>>> addCover() method that uses a physical layer to cover text. If you
>>> don't need it, just use setSelectable.
>>
>>
>>_______________________________________________
>>Dynapi-Dev mailing list
>>[EMAIL PROTECTED]
>>http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>>
> _______________________________________________
> Dynapi-Dev mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
