my suggestion is to call that method setPos(). same bytesize as moveTo() and consistent with the getXXX() and setXXX() philosophy. anybody?
-- Michael Buerge > From: Dan Steinman <[EMAIL PROTECTED]> > Date: Mon, 19 Nov 2001 13:12:35 -0500 > To: [EMAIL PROTECTED] > Subject: Re: [Dynapi-Dev] Proposed feature changes > > The reason I changed to setLocation is because moveBy and moveTo were very out > of place next to all the other methods of DynLayer: setX() setY() setSize() > moveTo() just doesn't make sense. > > And plus there are endless numbers of ways to get your 5 bytes back. > > My new anchoring system (which totally kicks butt btw) saves considerable file > size in widgets because you end up not ever having to call setLocation or > setSize because it's handled automatically. > > Dan > > On Mon, Nov 19, 2001 at 08:45:55AM -0800, Raymond Irving wrote: >> >> --- Dan Steinman <[EMAIL PROTECTED]> wrote: >>> Some of my changes in 2.6 are costmetic also, such >>> as setLocation() replacing moveTo(). >> >> It just hit me. Why change moveTo() to setLocation()? >> moveTo() consist of only 6 characters while >> setLocation() consist of 11 characters. In essence >> setLocation uses 5 byes more than moveTo. This might >> seem insignificant now but wait until numerous calls >> are made using setLocation. >> >> Just a thought! >> >> -- >> Raymond >> >> >> __________________________________________________ >> Do You Yahoo!? >> Find the one for you at Yahoo! Personals >> http://personals.yahoo.com >> >> _______________________________________________ >> Dynapi-Dev mailing list >> [EMAIL PROTECTED] >> http://www.mail-archive.com/[email protected]/ > > _______________________________________________ > Dynapi-Dev mailing list > [EMAIL PROTECTED] > http://www.mail-archive.com/[email protected]/ > _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/[email protected]/
