What was that thing with Photoshop images?

Peter Haworth pete at lcsql.com
Fri Aug 10 00:39:55 EDT 2012

Replying to all.

In general:

Patient to Doctor: "Doctor -  it hurts when I do this"
Doctor to Patient: "Well don't do that then."

That's my feeling about objects with the same name.

The engine allows duplicate names for objects (except stacks) so I'm not
sure how allowing control names for button icons adds any more new user

Jacque - I know about the button you mentioned but ti still results in an
image ID.  Here's the situation that caused me to ask the question.  I had
around 30 images I was using as button icons, some for the enabled state,
some for the disabled state.  I found a much better looking set of images
to use, imported them with new IDs.  Now I had to go through all my buttons
and change their IDs to the new ones.  Not a huge deal but if I had been
able to set the button icons to image names, I would have had to do nothing.

Plus Revolution makes a big deal about how English like and understandable
the language is, and rightly so.  Image IDs like 1004 tell you nothing
about where the image is in the stack while 'img "OpenStack" of Stack
"myImages" tells you exactly where to find it.

I don;t expect anything to change of course, just saying IMHO at least an
option to use image names would be more understandable and maintainable.
lcSQL Software <http://www.lcsql.com>

On Thu, Aug 9, 2012 at 8:21 PM, J. Landman Gay <jacque at hyperactivesw.com>wrote:

> On 8/9/12 7:43 PM, Peter Haworth wrote:
>> Why does the
>> Inspector allow only image IDs for button icons - object or file names
>> would be so much easier for maintenance purposes.
> What Scott said. While Mark's right that "lowest layer wins" would be
> logical, I think it would introduce yet another level of new-user
> confusion. Anyway, it's possible already to choose an existing image as an
> icon via the property inspector. Click the little button next to the icon
> ID field, choose "This Stack" from the popdown list, and click on the image
> you want to use.
>> Maybe this is why I see on the list that people use images instead of
>> buttons?
> If an image is static and only needs to respond to simple clicks or
> commands, I put a script in it. If I need scripted image changes
> (mouseovers, hiliting, state or status display, etc) I use a button.
> --
> Jacqueline Landman Gay         |     jacque at hyperactivesw.com
> HyperActive Software           |     http://www.hyperactivesw.com
> ______________________________**_________________
> 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<http://lists.runrev.com/mailman/listinfo/use-livecode>

More information about the use-livecode mailing list