Hi Rainer, not sure if I understand that right. You propose to test if each item copied to a database folder is already known to the database. And if it is, ask to hardcopy or just link it?
The problem is to have copies, clones and links mixed in one system. And many users might think that's all the same nor understanding the differences in detail. And as another caveat the users might not anticipate the future consequences if they choose one of them. Thus it might be a good practice to give them a second chance on a conflict. So it would be having a copy and a clone function. And when adding an item to a database folder on the workspace, the database must be probed for an already existing item with the same key. If there is a conflict the user has to choose from updating the database, using the item from the database or adding a clone. Puh, quite a big change. The tasks are: a) create an icon for "clone". And probably a better one for "copy" to make the difference visually obvious. b) add the clone option everywhere in the code where you find a copy option (workspace menu, item's screen options) c) add the database part to detect conflicts and add a dialog to resolve them. d) this has to be tested in all possible combinations. I can clearly see my name written on c). But a) and b) are a good chance for someone else to get familiar with the code. d) can be done by everyone, even those suffering codingphobia. Are there enough volunteers? Oliver ------------------------------------------------------------------------------ _______________________________________________ Qlandkartegt-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
