fix editor for double types that behave the same as floating point types

[TimGroeneboom]

Problem observed :

• The editor for double behave differently than float editor in Napkin, not allowing for more then 2 decimals and they show up with arrows, see video below

double_editor_bug.mp4

Proposed fix:

• Just like with enum types & combo boxes, check for the type and create a custom editor that behaves the same as a floating point editor, see video below

double_editor_fix.mp4

[Copilot]

Pull request overview

This PR adjusts Napkin’s property editor so that double-typed properties use a text-based editor with a double validator instead of the default spinbox behavior (limited decimals and arrow buttons).

Changes:

• Extend PropertyValueItemDelegate::createEditor to detect double properties via RTTI and create a QLineEdit with QDoubleValidator and strong focus instead of the default editor.
• Leave existing enum handling and default delegate behavior unchanged for other types.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.