BTW This is why I wanted to group my imported images into predefined ID ranges.
I ran across this at one point.
Bob
On Mar 31, 2012, at 7:21 PM, Timothy Miller wrote:
On Mar 31, 2012, at 3:56 PM, J. Landman Gay wrote:
On 3/31/12 5:34 PM, Timothy Miller wrote:
I just discovered that if I
It's one of the oddest things, but buttons point to imported images, imported
images *can* be set to point to a file on the hard drive. Why not allow a
button to point to an image on the hard drive for it's icon I say? Someone will
cry, Backwards Compatibility at this point no doubt. But the
I do not see what does not work in that context? The images does not
necessariely need to be imported? Works just fine with referenced images. Sure,
it still needs an image container, but that does not hurt much, does it? I
would be glad if the icon could be a rugged ID though (image ID 58 of
If a button could point to a file instead of an embedded image, the issues with
ID's would disappear altogether. Instead of having an image AND the button, and
then hiding the image, you would only have the button. Yes you can create an
image and point it to a file on the hard drive, but it
On 3/31/12 9:21 PM, Timothy Miller wrote:
What do I do with the little images I imported? Set the visible to
false, hide them under a field, or can I delete them now, because
they are used in a button?
You can't delete them; they are the source of your icons. Just set them
to be invisible.
On Mar 31, 2012, at 3:56 PM, J. Landman Gay wrote:
On 3/31/12 5:34 PM, Timothy Miller wrote:
I just discovered that if I click with the browse tool on the
place where the buttons should be, the button becomes visible and the
button script executes. If I save and quit LC, the buttons disappear
