Because of the fact that rhino-queues requires that you stop any application in order to inspect what's going on. The visualizer that was originally built didn't seem to make sense to maintain going forward. There is a sample linqpad file in the queues source that shows how to visualize what's going on. It isn't comprehensive, but it should get you in the right direction. If there is a way to at some point remove the requirement to stop the application to inspect, then a visualizer tool to be more important IMO.
-- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
