Surely the whole point of providing a duplication feature is to avoid having to use the native clipboard in Windows?
Sure, it is analogous (meaning comparable in certain respects) - it achieves the same goal but should not work the same way "under the hood". The implementation seems hacky.
I'd definitely be interested to hear other's opinion on whether this is expected behaviour to them in a modern application.
After-thought: this would only be expected behaviour if the button was called "Duplicate item and reset my clipboard for no apparent reason".
You asked for opinions. Mine is that using the Windows built-in clipboard is expected, and preferable to "Waste developmental and operational resources by recreating the wheel."
There's a difference between re-creating the wheel and using "hacky" shortcut implementations that don't benefit the end-user, just to save time in development.
If we were still in 2012 I'd probably agree with you... however it's almost 10 years later, software and development has evolved!
Could it not at least be considered that the content in the clipboard is restored, rather than being reset?
That's the actual issue I'm trying to raise here. The user duplicates an item and their clipboard is reset. Their clipboard contents should be restored, no matter what method Storyline is using to duplicate instances.
7 Replies
That is expected behaviour duplicate is analogous to copy and paste
Surely the whole point of providing a duplication feature is to avoid having to use the native clipboard in Windows?
Sure, it is analogous (meaning comparable in certain respects) - it achieves the same goal but should not work the same way "under the hood". The implementation seems hacky.
I'd definitely be interested to hear other's opinion on whether this is expected behaviour to them in a modern application.
After-thought: this would only be expected behaviour if the button was called "Duplicate item and reset my clipboard for no apparent reason".
You asked for opinions. Mine is that using the Windows built-in clipboard is expected, and preferable to "Waste developmental and operational resources by recreating the wheel."
There's a difference between re-creating the wheel and using "hacky" shortcut implementations that don't benefit the end-user, just to save time in development.
If we were still in 2012 I'd probably agree with you... however it's almost 10 years later, software and development has evolved!
This implementation should be re-considered.
Could it not at least be considered that the content in the clipboard is restored, rather than being reset?
That's the actual issue I'm trying to raise here. The user duplicates an item and their clipboard is reset. Their clipboard contents should be restored, no matter what method Storyline is using to duplicate instances.
I spoke with the engineers about this in the early days of storyline and it is expected behaviour.
I think the clipboard should be restored, but it isn't and I have adjusted my workflow so it doesn't bite me.
Great to see this has now been resolved! Thanks