LiveCode Forums.

Hello,
For a game I'm developing, I've implemented an inventory system. When you interact with an image, its visibility is set to 'false,' and the name of the image is added to a spare inventory 'slot' in an SQLite database.

When you select the item in a data grid and click the 'drop' button, the corresponding database entry is removed, and the image's visibility is set back to 'visible.' I know this might make me sound like a total beginner to the experienced coders here, but that's my approach.

1. The main issue with my current method is that when you move between cards (or 'rooms' in my game), the image doesn’t transfer with you. While the database entry in the inventory travels with you, you can't drop items in different cards because they are tied to a specific card.

2. Is there a better way to handle this before it's too late? I’m working on a demo game to learn and avoid fundamental mistakes that could cause problems later on.

3. Can I make the object move to the current card if the player chooses to drop it in a different room?

Hi Charles,

welcome to the forum!

Hm, I would probably use a couple of BUTTONs, one on each card where neccessary,
with the image you need as the ICON for the button.

This way, you can show/use your imge on many cards, but the image is only "physically"
present ONCE in your stack.

Know what I mean? Drop a line if not!

Best

Klaus

One option would be to use a shared group that is placed on all cards. When the object is hidden it could be placed into this inventory group. When you unhide the item you would also need to move it out of the group. The way the shared group works would allow the image to be available on all cards.

Charles (?)

Sounds like you are pretty well along for a "beginner". Some questions:

Is there a single image or are there multiple ones, depending on the card?
Whatever image there is, is that the first place the user is supposed to interact?
You said "When you interact with an image, its visibility is set to 'false". How does the user terminate that interaction, in order to hide the image?

I am trying to understand the process. Oftentimes for me, rethinking the entire methodology has made my life much simpler.

Craig

Hi Charles,

welcome to the forum!

Hm, I would probably use a couple of BUTTONs, one on each card where neccessary,
with the image you need as the ICON for the button.

This way, you can show/use your imge on many cards, but the image is only "physically"
present ONCE in your stack.

Know what I mean? Drop a line if not!

Best

Klaus

I know what you mean. Thanks for your advice.