LiveCode Forums.

Hi all,

Hope you all can help. I have a main stack and a sub stack which stores 95% of my images.

However I have run into a problem as some of the objects I have added in the main stack have the same IDs as the the sub stack and this is causing problems.

Is there fast/automated way to check if there is any conflicts/duplicate IDs across both stacks? or a fix for this problem?

thanks

HI istech,

what problems are you experiencing?
Duplicate IDs in different stack is normal behavior!

You could script a solution to check the IDs, but maybe this is not neccessary.
But therefore we need to know the problem!

Remember that you can change objects IDs if you really want to, at your own risk of course
But that makes sense when it comes to IMAGE ID conflicts!


Best

Klaus

I suggest to not use ID's in all places where you have a choice. I think the only places where you have to use id's are icons and behaviors.

Hi,

The problem I have run into is when I import images from a folder into the sub stack and use them as icons in buttons etc in the main stack.

Some of the objects share ids on the main stack so when I reference a image(using a id) from the sub stack I get a main stack image(etc) from time to time.

As I continue moving through the project creating new buttons or players etc this issue can cause problems. Is there a solution for this?

I hope this makes sense.

ps. and yes Klaus I have had to change quite a few...of the ones I found

IDs are settable. Tedious, but you could change the ID values from the ones they were imported with to make them unique across your project.

Thanks Richard,

Yes this has been the case. Just checking to see if there was any other faster method.

I suppose it would be nice to see all the IDs in the application browser under a separate column. I could then do a sort and see if there are any duplicates among the stacks.

In any case thanks for your replies.

Ah i see, an image library substack. One way that I made work before is to set the id of the substack to a high value, for example I tend to use 300000. That way, all id's of new objects will start from there, which reduces the likeliness of conflicts.

Yes in fact I started to do this and made it 500 away from my main stack IDs.

In the end it was no way enough looks like IDs 30k and above is the option.