View Single Post
  #11   Spotlight this post!  
Unread 31-12-2006, 12:46
esquared's Avatar
esquared esquared is offline
Keeps saying 3-2-1-Rush...
AKA: Angry Eric
no team (Volunteer!)
Team Role: Mascot
 
Join Date: Jan 2006
Rookie Year: 2005
Location: Boston, MA
Posts: 192
esquared has a reputation beyond reputeesquared has a reputation beyond reputeesquared has a reputation beyond reputeesquared has a reputation beyond reputeesquared has a reputation beyond reputeesquared has a reputation beyond reputeesquared has a reputation beyond reputeesquared has a reputation beyond reputeesquared has a reputation beyond reputeesquared has a reputation beyond reputeesquared has a reputation beyond repute
Re: Visual C++ 2005 Designer

I'm not in front of VC++ right now, but typically there is an Object Browser or that type of thing that allows you to view objects, variables, arrays, pointers, etc when running the program in debugging mode. It might just be part of their debug menu to watch variables, etc. I would watch both the main pointer, and the main MdiParent object itself. You should be able to follow the pointer in the watch menu to see it correctly reference the class's methods, members, etc. Again, since I'm not in front of the IDE I can't give you more specific names to look for.

The idea you've come up with seems pretty useful, the only question will be the overhead on the serial port/quantity of interrupts if your RC is interrupt heavy. It was somewhat difficult to tell from the GUI screen, but how many bytes of data will be sent per "GUI update"? And this will be called every "slow loop" to update or every "fast loop"?