Open patrickdalla opened 10 months ago
Could we create a separate bookmark.iped file specific for the multicase? Any modification would apply to this separate bookmark.iped for the multicase, keeping the original single case bookmark.iped. Also, when opening a multicase, if bookmark conflicts are identified a merge warning could be shown.
On the other hand, maybe the user wants to replicate the bookmark changes to the single cases.
Could we create a separate bookmark.iped file specific for the multicase? Any modification would apply to this separate bookmark.iped for the multicase, keeping the original single case bookmark.iped. Also, when opening a multicase, if bookmark conflicts are identified a merge warning could be shown.
On the other hand, maybe the user wants to replicate the bookmark changes to the single cases.
Hi @patrickdalla, I think popping up a warning if conflicts are identified is a good idea! In my opinion we could use a separate bookmarks.iped
for the multicase just in this conflict situation (and also warn the user about that), and keep current behavior of replicating bookmark changes to single cases if there is no conflict.
Hi @patrickdalla, I think popping up a warning if conflicts are identified is a good idea! In my opinion we could use a separate
bookmarks.iped
for the multicase just in this conflict situation (and also warn the user about that), and keep current behavior of replicating bookmark changes to single cases if there is no conflict.
How might be a subsequent opening of this multicase with these bookmarks saved on a distinct file?
If two or more cases with bookmarks with same name, but some different properties like comment, color and shortcut are opened inside a multicase IPED opening, one of this bookmark is chosen from one the cases and the properties of the remaining bookmarks of the others cases are overwritten with the properties of this bookmark.