Thread: Custom Dashboards and the Driver Station Software
View Single Post
  #4   Spotlight this post!  
Unread 30-03-2010, 20:43
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
  
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Custom Dashboards and the Driver Station Software
Maybe I misunderstood the original question. Is the issue that two DBs run when the Driver starts, or is the issue that fast-user-switching results in a DB running in both Driver and Developer?

If it is the second, then you can solve this similar to how the DS does. You identify a resource owned by the DB -- it can be a file or a network connection. When the second app fails to acquire the resource, it sends a message to the first instance to commit hara-kiri. The second then sleeps and tries again until the first releases the resource. As a fallback, the second can give up and decide it lost the battle and exit with a message or something.

Greg McKaskle