Quote:
Originally Posted by Peter Johnson
SmartDashboard should be in 11.2... at least I'm generating wrapper code for it. I've not tested it yet, but it should work, something like:
Code:
ds = wpilib.DriverStation.GetInstance()
dash = wpilib.SmartDashboard(ds.GetUserStatusDataSem())
ds.SetHighPriorityDashboardPackerToUse(dash)
I'm definitely working hard on the image processing stuff. Is it just the vision/vision2009 libraries that are useful, or do people really use a lot of stuff in nivision directly as well? Nivision is very large and raw C (rather than C++) so it's taking a lot of time to wrap it.
SIP is a good place to start, although SWIG can be used as well (although if your classes extend WPILib classes you'll need to use SIP). The next step is to check out the codebase (from git) and look at how the various packages are wrapped (WPILib namely). |
OK, got the SmartDashboard working on the robot side with your example code - thanks! Something funky happening on the SmartDashboard client side though: each Log() call seems to create a new widget; I'll have to investigate this further.
I think the vision/vision2009 interfaces have been the most useful to us up 'til now; we have not yet had to delve into the IMAQ functions. Looking for functionality akin to the 2010ImageDemo, essentially.
Cloned the git repository; learning SIP is next on our list. Having it in the toolbox also might provide an escape valve for situations where wrapping an entire C++ lib might be too much work, in which case we could just wrap customized code that implements only the functionality necessary.