Hey everyone, I'd first like to anwser a few questions:
I was going to use
windows registry and .Net built in functions to save my applications working state (i.e. is it playing a song, or was the gps
software running. They way we normally do things to remember settings) I've found it SO much easier to tie everything into the database that my media files are going to be stored in..
In fact every media file is just going to be a class that has intrensic controls within itself. (i.e. it plays it self, knows its own working state) In the database, the working media file will have a field called "playing" and "position" only one song in the audio table of the database will have playing=true So when the ignition is cut from the carputer and
power is lost to the system.. It will easily be able to recall what it was doing.
When the software starts, it goes to the GUI table in the database (code posted above) It checks the database to figure out what was opened. Then an event handler goes ahead and opens each feature in my software.
Each feature, then calls its own table of settings in the database (via SQL) and remembers what it was doing before the ignition was cut.
Whats your thoughts about doing this through database ?? I really think it streamlines the coding a hell of a lot better.
Bookmarks