<div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">* ControlElement: a class that implements the idea of a control element.<br>
each subclass would implement something like "launch configuration" or<br>
"rotate". subclasses would be tagged with a semantic enum much as we have in<br>
AbstractToolBox::ToolType. ControlElement would accept input events.<br>
<br>
* AbstractHandle: a class that would paint and manage a handle along with<br>
zero or more ControlElements<br>
<br>
then ... an AbstractHandle (or a subclass of it, really) would be assigned a<br>
QGraphicsWidget(/Object?). when being shown, it would check to see if the<br>
controlElement property exists on the object. if it does, it would request<br>
those ControlElements and use them to figure out which ones to show (e.g. it<br>
might avoid geometry changing elements) and pass on input events to those<br>
elements as appropriate.<br></blockquote><div><br>Interesting approach, i like it. <br>There's just a thing i'm not sure i understood well. You said to check if there is the controlElement property. Do you mean having a property for each control element the widget accepts? <br>
</div><div> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Giulio: since you are the one most affected by the "usable with any<br>
QGraphicsWidget/Object" issue, would you be interested in taking on the<br>
design of ControlElement?<br></blockquote><div><br>Tomorrow i'll go away for something like three weeks, so I won't be able to do anything until the end of august, but after that i'm certainly interested in doing this.<br>
</div><br></div>Cheers, Giulio<br>