Image Scaling Problem
blueback09 at gmail.com
Tue Jan 19 20:17:05 CET 2016
Oh, okay. So if you resize it and then use lockLoc to keep it there what
you're seeing is a modification of the original image and if you reverse
lockLoc you throw out the modification and go back to the original image.
But if you set the imageData to the imageData you overwrite the original
image so that all you've got left is the resized image. Is that correct?
On Tue, Jan 19, 2016 at 11:11 AM, Klaus major-k <klaus at major-k.de> wrote:
> Hi Richmond,
> > Am 19.01.2016 um 19:33 schrieb Richmond <richmondmathewson at gmail.com>:
> > On 19/01/16 20:24, Mark Wieder wrote:
> >> On 01/19/2016 10:07 AM, Richmond wrote:
> >>> On 19/01/16 17:27, Matt Maier wrote:
> >>>> I was just researching around this idea.
> >>>> This says that if you want to lock the change in by script you have to
> >>>> set
> >>>> its imageData to its imageData
> >>>> set the imagedata of image tImageName to the imagedata of image
> >>>> tImageName
> >>> Nobody ever told me that, and I've been resizing images, locking them
> >>> and having
> >>> no further problems since 2001.
> >> That's for an entirely different scenario.
> > Possibly:
> > Are you stating that if I pop this in my messageBox:
> oh boy…
> > ## set the locked of img "XXX" to true
> set the lockloc of img "XXX" to true
> > it, somehow, does something 'less' than locking the image via
> > the properties panel?
> > Because, when I did that just now, saved the stack, quit LiveCode,
> restarted LiveCode,
> > and opened my stack again, the image 'XXX' was still at its resized size.
> Yes, no surprise, see above… 8-)
> > Please, in simple words, explain what the "entirely different scenario"
> > Richmond.
> Klaus Major
> klaus at major-k.de
> 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