--- Doug Melvin <[EMAIL PROTECTED]> wrote:
> > In the ChangeLog Dan had suggested that the
> onresize
> > event be replaced with the setAnchor() function.
> The
> > setAnchor() function is much more flexible that
> having
> > to do invokeEvent("resize")
>
> So how do I respond to the resizing of a layer?
> I really would like to know.
These are issues we will have to collaborate on. Is it
best to add invokeEvent inside the setSize() function?
How many apps/widgets will make use of the onresize
events? The pros and cons will have to be carefully
look at. Having invokeEvent inside setSize will slow
down animations and layers/widgets that makes use of
the anchor feature. If you say yes add the onresize,
then you'll have to add the onmove,etc events that
have been removed.
DynAPI 3.0 removed the onresize and onmove events. IMO
I don't think we need these events. I've found other
ways to solve my resize issues, but let's get some
feedback from the other developers.
Should be sacrifice add onresize,onmove and onload
back into 3.0?
We have about 7 active debvelopers, let hear the view
of as many as posible.
> >
> > As for onload... It was suggested the the
> onCreate()
> > onPrecreate() functions be used to trigger
> callbacks
> > once the object (elm) is loaded.
>
> See previous email (if it ever arrives on the
server)
same as comment above.
--
Raymond Irving
__________________________________________________
Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
http://platinum.yahoo.com
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://www.mail-archive.com/[EMAIL PROTECTED]/
