Laurent Veilleux wrote:
> I think the current tools : select and move could just be extended by
> giving more options in args , like the classname of object we expect
> (pin in this case)  and the depth level (1,2,3,infinit) of the search
> on child
>   
Pins are only direct childs of  the object which or children of the top 
object in a view.
so only two deep is needed.

> About the event I want to implement it's just to get the pin
> properties (name,I/O) and print them in an control to edit them, so I
> think the best solution is to generate a "pinCliked" event with all
> this data from the tool and it will go to the canvas and then to the
> main window , or directly to the main window dunno currently , I will
> see
>   
For this i would indeed generate an event from the tool, and sent it to 
the wxEventDistributer.
Next you can have a modeless dialog (which opens at the first pin 
click), and which receives this event.
a2dComEvent  is best for this i think. Search sttool.cpp for some examples.

a2dStToolEvtHandler::OnComEvent() creates one for editstart.









-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Wxart2d-users_dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wxart2d-users_dev

Reply via email to