Group: Forum Members
Posts: 1,
Visits: 4
|
Hello, I'm sorry to resurrect an old thread.
But we're having a similar issue where we have a project with 11 rooms, they are very similar, but different. When designing the original system we "cloned" the first one and began making changes to each subsequent room. However, when we go back to the original, any of the changes that were made to say a text field, or keynote have all changed. So we're having to go back and copy/paste each one of these instances so to create a unique ID for each room page.
This would have been so much more intuitive if the 'cloned' items were given there own unique ID upon creation. I can somewhat understand the reasoning behind not wanting many different instances of an object, as that eventually plays a role in the file size, cache, and processing power. However, for ease of use for the user, this should either be made ABUNDANTLY clear, or it should be set up as how most users would assume it works. This would have saved us hours of time knowing that we should copy paste from tab to tab, rather than simply clone a tab.
We'll only make that mistake once, hopefully.
|