20,741
edits
Howto:Processing legacy PUI dialogs using Canvas: Difference between revisions
Jump to navigation
Jump to search
Howto:Processing legacy PUI dialogs using Canvas (view source)
Revision as of 19:37, 25 January 2017
, 25 January 2017→Preliminary Findings (core Canvas/C++)
| Line 2,256: | Line 2,256: | ||
This section is intended to gather data points and conclusions to identify bottlenecks and potential opportunities for optimizing Canvas, unrelated to the UI use-case, but with a focus on shaping APIs that may be useful for similar efforts, such as e.g. porting the HUD/2D panels code to use a similar approach: | This section is intended to gather data points and conclusions to identify bottlenecks and potential opportunities for optimizing Canvas, unrelated to the UI use-case, but with a focus on shaping APIs that may be useful for similar efforts, such as e.g. porting the HUD/2D panels code to use a similar approach: | ||
* for testing purposes it would make sense to come up with a dialog showing an embedded Canvas to open/run arbitrary dialogs on demand (including aircraft specific ones) | |||
* at least on old hardware, instantiating a Canvas-based PUI dialog is a fairly noticeable process that may take 50-120ms | * at least on old hardware, instantiating a Canvas-based PUI dialog is a fairly noticeable process that may take 50-120ms | ||
* wrapping key props.nas APIs via cppbind would certainly help speed-up dialog parsing/processing | * wrapping key props.nas APIs via cppbind would certainly help speed-up dialog parsing/processing | ||