From: Robert R. <rra...@ya...> - 2000-12-07 19:40:05
|
If its OK, I can move the DynAPI images methods into DynImage. I've already done this with my local copy, and every thing is working fine. If we do this and remove images.js, then the scrollpane will also need to be changed so that is uses DynImage.getImage(). This can easily be done, and if there are no objections, I can make the changes. -- // Robert Rainwater On 12/7/2000, 3:01:22 PM EST, Dan wrote about "[Dynapi-Dev] getImage": > DynImage.getImage() isn't the same code as DynAPI.getImage() > I wasn't really sure what to do with the getImage. There's not much point in having both an /ext/images.js files and a /gui/dynimage.js. I think maybe the /ext/images.js code should be moved into > dynimage. The DynImage widget is very small and much more handy than I would have expected. > A future addition to DynImage would allow it automatically resize itself based on the image's true w/h - this is not possible until someone code's in that ability. > Dan > On Wed, Dec 06, 2000 at 06:33:22PM -0800, Scott Andrew LePera wrote: >> May I humbly suggest restoring the optional width and height arguments >> to the DynImage.getImage method. It's a real pain when I have to wait >> for the image to be fully loaded before I can access the height and >> width. I'd rather pass these values in advance when I can. >> >> -- >> scott andrew lepera >> ----------------------------------- >> web stuff: www.scottandrew.com >> music stuff: www.walkingbirds.com >> _______________________________________________ >> Dynapi-Dev mailing list >> Dyn...@li... >> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev |