nd 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. T
Okay, that's my fault because I totally forgot that DynAPI.getImage was
moved to the images.js extension ::smacks forehead::
Dan Steinman wrote:
>
> 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 ha
y a simple
browser launch.
Unfortunately, NS6 is such a 'rendering' nightmare it will only HELP MS
capture more marketshare.
DS
- Original Message -
From: "Nuno Ferreira" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, December 07, 2000 8:33 AM
quinta-feira, 7 de Dezembro de 2000 2:33
To: dynapi
Subject: [Dynapi-Dev] getImage
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 an
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 ve
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
---
