| 12345678910111213141516171819202122232425262728293031323334353637383940 |
- TODO:
- - Callback on tree item select
- - Clicking on an already selectecd element starts rename
- - Will likely need some kind of check to ignore double-clicks?
- - Context menu with rename/copy/paste/duplicate
- - Delete with Undo/Redo support
- - Auto scroll
- - Sliding over top or bottom of the tree view while dragging an element will search GUIElement parents to find a ScrollArea. If it finds one it will attempt to scroll up or down.
- - Support for icons next to tree elements
- - Ability to move selection via arrow keys
- Drag and drop problem:
- - Test it properly
- If I make three element deep tree
- A
- --B
- ----C
- And the move C to have parent A, nothing will happen when I first do it. And when I do it next time element will move properly but a ghost element will remain.
- MenuBar problems:
- - Clicking the top menu item closes and immediately opens the menu again (it should only close it)
- - Something similar probably also happens with ListBox
- Other:
- - When dragging in tree view automatically expand mouse over elements
- - "Ping" effect
- - Copy/Paste/Duplicate
- - This is more of a problem with actual copying of SceneObjects (It's not implemented). I should be able to serialize, and then de-serialize with a new parent as a form of copy.
- --------------------------------------------------
- LOW PRIORITY:
- Shoutcuts ideas:
- Remove Cut/Copy/Paste/Undo/Redo/Rename/SelectAll and similar shortcuts from InputCommands. Instead send generic shortcut commands whenever user presses some key (with shift/ctrl/alt state).
- - I will need some kind of generic shortcuts at some point so there is no point that Rename is hardcoded to F2
- - I should also add a GUIShortcutManager, as a centralized place for dealing with shortcuts (so that I my edit them at a later date)
- - TODO - Figure out how would this work. How would the centralized system know all of the UI shortcuts? Probably register them somehow on program start?
- - This shortcut system would be separate from the input manager, and would not be meant for in-game use
|
