Hi,
[quote user="zCane75"]... it looks like the issue with my solution is the double click.[/quote]
No, the double click itself is only a consequence of the primary problem, which is wrongly designed tool with a behaviour not compatible with MicroStation UX standards. It leads to users confusion and a side effect is it requires more development effort, because API doesn't offer such functionality by default.
[quote user="zCane75"]But I still don't see any function that will get a selected point in a C# addin from a single click in Microstation.[/quote]
As Jon wrote, IXxxCommandEvents interfaces are the way you have to go. To use any other construction / solution to implement a user tool that creates, modifies or use MicroStation elements than them is pretty bad idea.
There are two interfaces available in VBA and NET API:
- IPrimitiveCommandEvents is typically used when a tool creates new element(s). It provides more flexibility comparing to ILocateCommandEvents, so it's used to implement more complex workflows also (e.g. when element is created based on location of another element).
- ILocateCommandEvents is used for tools that require to locate element to do something (delete element, change it, start analysis of the element etc.).
See examples in MicroStation VBA help how to work with these constructions. Because NET API allows also to work with Tool Seettings window (not possible in VBA), also check NET examples available in MicroStation SDK and search for AttachToToolSettings(addin) method.
With regards,
Jan