Button Icon IDs

Peter Haworth pete at lcsql.com
Fri Oct 24 17:55:15 EDT 2014


Excellent, thanks Monte.

Pete
lcSQL Software <http://www.lcsql.com>
Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and
SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html>

On Fri, Oct 24, 2014 at 1:12 PM, Monte Goulding <monte at sweattechnologies.com
> wrote:

> Use the resolve command. I implemented this to do exactly what you want:
> get the long id of the image that is used on an icon on a given button. You
> have to specify the button because that's what the icon is resolved
> relative to. It uses the same code the engine does to find the icon btw.
>
> Cheers
>
> Monte
>
> --
> M E R Goulding
> Software development services
>
> mergExt - There's an external for that!
>
> > On 25 Oct 2014, at 4:22 am, Peter Haworth <pete at lcsql.com> wrote:
> >
> > When setting the icon of a button, there is a hierarchy of locations that
> > LC uses to find the image.  However, if I subsequently try to reference
> the
> > image id in a script, LC won't find it unless I fully qualify where it is
> > (unless it's on the current card of course).
> >
> > I want to set the height and width of the button to the height and width
> of
> > its icon image.  Is there any way to find the location of the icon image
> > from its ID?
> >
> > Pete
> > lcSQL Software <http://www.lcsql.com>
> > Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and
> > SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html>
> > _______________________________________________
> > use-livecode mailing list
> > use-livecode at lists.runrev.com
> > Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



More information about the use-livecode mailing list