20,741
edits
Canvas widgets: Difference between revisions
Jump to navigation
Jump to search
m
→C++ core requirements {{Pending}}: show-dialog can be overwritten via removecommand/addcommand from Nasal space
m (→Widget declaration: XML vs. Nasal: rm section, hardly relevant any longer) |
m (→C++ core requirements {{Pending}}: show-dialog can be overwritten via removecommand/addcommand from Nasal space) |
||
| Line 110: | Line 110: | ||
* It would be also be good to allow the canvas textures to be resized at runtime, so that we don't have to reserve to large canvases just because the dialogs could be resized. {{Pending}} | * It would be also be good to allow the canvas textures to be resized at runtime, so that we don't have to reserve to large canvases just because the dialogs could be resized. {{Pending}} | ||
* The GUI system should take care of handling and forwarding mouse and keyboard events to the property tree as needed (Some parts of the existing code could probably be reused). Eg. if a canvas is assigned picking should occur on mouse clicks and forwarded to the property tree. {{Pending}} | * The GUI system should take care of handling and forwarding mouse and keyboard events to the property tree as needed (Some parts of the existing code could probably be reused). Eg. if a canvas is assigned picking should occur on mouse clicks and forwarded to the property tree. {{Pending}} | ||
* The existing dialog-show command needs to be modified to call the according function in Nasal space which will handle the whole creation and updating of the GUI. {{Pending}} | * The existing dialog-show command needs to be modified to call the according function in Nasal space which will handle the whole creation and updating of the GUI. {{Pending}} (can be done by using the new removecommand/addcommand APIs meanwhile) | ||
=== Keyboard Handling === | === Keyboard Handling === | ||