You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the explanation and demo, that makes a lot of sense. I can't help but favour the plugin's behaviour of turning a shadow block into a real block on edit - since that shows intent from the user to make something concrete. Are there situations or applications in which this wouldn't make sense, or previous discussions I can refer back to learn about the competing needs?
There are downstream consequences of this behaviour on copy and paste, which don't make up with my expectations. I would have assumed you'd be able to copy and paste the contents of an oval, like the text in a "write with shadow" block
I would naively argue that these blocks should be real, and draggable, and copyable. If they are not, then we definitely need some user feedback when they try to copy a block, because currently copy will silently fail and you'll end up surprised by pasting the last thing in the copy buffer.
Shadow blocks can't be copied, likely due to checks for isDeletable and isMovable in blockCopyPreconditionFn in navigation_controller.ts.
It should be possible to copy them, since users can't tell which blocks are shadows and which aren't in Zelos. (I think it should also be possible to copy them in Geras). However, the block needs to be converted from a shadow block to a real block either on copy or on paste.
Originally posted by @kmcnaught in #132
The text was updated successfully, but these errors were encountered: