merakosp at gmail.com
Fri Feb 22 02:39:57 EST 2019
Thanks for your kind words, Hermann.
Indeed, the property name "size" might be confusing, but it has been like
this for ages, so changing it now will break existing scripts.
In the property inspector, if you change the settings to show the
"Description of option" rather than the "Name of LiveCode property", then
it says "Size in bytes". At least this might clarify things for newcomers.
We could add a note to the dictionary though, including what is NOT the
"size", as you accurately described it in your previous post.
On Thu, Feb 21, 2019 at 10:15 PM hh via use-livecode <
use-livecode at lists.runrev.com> wrote:
> Release 9.0.3 RC-1:
> Thanks Panos (especially) for your work of the last months.
> The "size" field for images disappeared a while ago and is now back.
> TMHO the name "size" may be misleading. It is
> = not the size = (width, height) of the image,
> = not the size of the raw data (=4*formattedWidth*formattedHeight) in
> = not the filesize of the image when saved as single image to disk (which
> depends on the image format, thus it is empty for referenced images),
> = not the size of the LC image representation in RAM (which depends on the
> resizeQuality of the image) in Bytes.
> It is the size of the image in Bytes when saved as part of the stack to
> So a valuable info.
> But perhaps it could be called "sizeInStack"?
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the Use-livecode