Ghost

[X4]

The problem / use case
Moving text using traditional Cut & Paste is flawed:

• Overwrites Clipboard: Cutting replaces existing clipboard contents; undoing restores the document text but loses the previous clipboard data.

• Document Reflow: Cutting immediately shifts text layout, making it harder to maintain visual context and relocate the target insertion point.

• Non-Atomic Operations: Moving text requires separate cut and paste steps, making single-step undo impossible—especially if intermediate edits occur.

What you'd like
Implement "Ghost Cut" functionality for moving text/images/objects:

• Faded/Inert State (Ctrl+X / Cmd+X): Selected text fades and becomes non-interactable (uncopyable, unclickable, cursor skips over it) while remaining visible in place without altering the clipboard.

• Cancel (Esc): Restores the ghosted text to an active, editable state.
  Atomic Move (Ctrl+V / Cmd+V): Removes the ghosted text/images/objects from its origin and inserts it at the current cursor position as a single, fully reversible move operation.

See: https://ishmael.textualize.io/blog/ghost-cut/

[senthan-07]

I've opened PR #97 implementing Ghost Cut support for canvas/slide elements.

The current implementation covers moving slide objects such as text boxes, images, shapes, charts, and other canvas elements. It intentionally does not implement Ghost Cut for inline text selections while actively editing text inside a text box, as I wanted to keep this change focused and easier to review.

Feedback is very welcome. If it makes sense, I'd be happy to work on inline text editing support as a follow-up enhancement.

[nyblnet]

Thanks for creating the PR! I actually like this ghost cut functionality but also keenly aware that most people might find it different and may be confused. I think it can be an option if it is very small or if I am able to finalise a extensions system so it can be installed as a pack. I'll a bit with you PR and see.

[senthan-07]

Thanks for taking a look and for the feedback! That makes total sense about avoiding potential user confusion.

I'm happy to add a configurable setting (disabled by default) so users can opt in, or adapt it for the extension system

Let me know how your testing goes or if you'd like me to go ahead with the setting toggle! In the meantime, I'll clean up the merge conflicts with main so the branch stays fresh.