...since it would be problematic, so store the prospective context data for any conceivable gesture within each Widget possibly addressed by that gesture. After some mulling over, today it finally occurred to me, that I already solved a similar problem for the layout management, and the very structure of ViewModel vs. Widget vs. Canvas settles around that solution. Thus we could try to expand that structure -- which means that the gesture context is only created *late*, when the gesture starts; and then the *subject* should be reponsible to collect and establish the context for the gesture and feed it to the gesture-controller, not the other way round |
||
|---|---|---|
| .. | ||
| draw | ||
| DIR_INFO | ||
| empty.html | ||
| InterfaceConcept_Varga.mm | ||
| renderengine.html | ||
| thinkPad.ichthyo.mm | ||
| uml | ||
| workflow.mm | ||