20,741
edits
Talk:Hackathon Proposal: CompositeViewer and Canvas: Difference between revisions
Talk:Hackathon Proposal: CompositeViewer and Canvas (view source)
Revision as of 17:09, 16 November 2020
, 16 November 2020no edit summary
(→interface properties: new section) |
mNo edit summary |
||
| Line 15: | Line 15: | ||
::: --[[User:Icecode|Icecode]] ([[User talk:Icecode|talk]]) 11:55, 16 November 2020 (EST) | ::: --[[User:Icecode|Icecode]] ([[User talk:Icecode|talk]]) 11:55, 16 November 2020 (EST) | ||
:::: so that means, draw masks (node masks) per compositor and LOD ranges need to be mapped to the view element then (see below), right ? And a dedicated prerender camera outside the scene graph for just MFDs ? --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 12:09, 16 November 2020 (EST) | |||
== aircraft-less prototyping == | == aircraft-less prototyping == | ||
| Line 21: | Line 22: | ||
== interface properties == | == interface properties == | ||
sooner or later, each view element would require a handle to the relevant properties to set up/manipulate the associated compositor (node masks, effects, LOD) and the view manager used by that view. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 12:07, 16 November 2020 (EST) | sooner or later, each view element would require a handle to the relevant properties to set up/manipulate the associated compositor (node masks, effects, LOD) and the view manager used by that view. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 12:07, 16 November 2020 (EST) | ||
{{Appendix}} | |||