Two problems:
1) I just spend a considerable amount of time assembling a list of my best Themes. When I am starting up the stand alone app and select my themes there is no change whatsoever.
2) How do I access the toolbar when activating the screen saver from within iTunes without quitting out of G-Force?
I think this is a great program, I love it apart from these little niggles.
Saved themes don't respond when selected
Moderators: BTT, andy55, b.dwall, juxtiphi
Purely a guess on my part, but I would ASSUME that themes are implemented by a call to:
void SetAllEnabled( int inConfigType, bool inIsEnabled ); // Enabling ALL, setting 'inIsEnabled'=1
FOLLOWED by subsequent calls to:
void SetItemEnabled( int inConfigType, string inName, bool inIsEnabled ); // actually Disabling, setting 'inIsEnabled'=0
accessing each entry in the theme file:
...G-Force\Themes\Your Theme Name\theme.txt
on Windows machines (anyway).
The question is if this action is something local to/implemented as part of the toolbar, or can an equivalent action be preformed as a startup procedure (i.e., for the ScreenSaver)
I CAN NOT find an example/documentation for reading the theme.txt files. Their format (except for the header) is straight forward enough. I would think that this may need to be addressed by Soundspectrum as a trouble report/question.
I do NOT use themes, but when I change them using the Toolbar to one of the one's supplied, and then go check if the config file is ACTIVE(checked) under its respective slideshow list, FOR ME, things seem copacetic ... not true for you? It also seems to retain the theme, upon subsequent Standalone invocations, so just MAYBE there is an undocumented 'Pref' available...
Sorry I can't provide better news/answer ...
One more thought, I run on XPro32/sp3 and have the task manager opened all of the time. MANY MANY times, the Standalone executable and/or the ToolBar do NOT experience timely deaths and I have to use the task manager to finsh them off. If rouge zombie processes exist, I sometimes experience unpredictable behavior from subsequent Standalone/Toolbar invocations. I am NOT sure how this applies to the Mac, but in the UNIX world 'kill -9' would do the trick!
ScreenSaver Issue Update
I found THIS:
The Preferences File
The G-Force preferences file is a "config" file, meaning it’s a plain-text file simply containing a list of values (in no particular order). Its file format is intended to be learned extremely quickly; the format is described in the config programming section. The purpose of the preferences file is to allow various user variables (ex, window position, full screen resolution, visual reactivity settings) to persist from each time G-Force is run to the next. Since G-Force only writes/updates its preferences file when it exits, you must run and exit G-Force at least once before you (or the ScreenSaver, hmmm??) will be able find it. On Windows, preference files are located in C:\Documents and Settings\Application Data\SoundSpectrum\G-Force" and on Mac OS X, they are located in "~/Library/Preferences/SoundSpectrum/G-Force".
D:\Documents and Settings\Jerohm\Application Data\SoundSpectrum\G-Force\Toolbar Preferences.txt :
:
Theme.Name = "Black Background ColorMaps"
:
doesn't look TOO Promising ... I would bet it is implemented in the Toolbar and NOT accessed by the Screensaver
However, in the same directory are these three files:
'Disabled WaveShapes.txt'
'Disabled FlowFields.txt'
'Disabled ColorMaps.txt'
which contain 'theme-ish' info about the LAST invocation. When MY screensaver starts up, it seems to run in the same state as I last left it in when exitting Standalone Mode. Seek out these files and take a look. (I AM running the Beta however).
What I am thinking is that BOTH your issues are related. Get comfortable that you can set the Standalone/Toolbar themes ... and they should carry over when the screensaver starts up.... just talking to myself.
void SetAllEnabled( int inConfigType, bool inIsEnabled ); // Enabling ALL, setting 'inIsEnabled'=1
FOLLOWED by subsequent calls to:
void SetItemEnabled( int inConfigType, string inName, bool inIsEnabled ); // actually Disabling, setting 'inIsEnabled'=0
accessing each entry in the theme file:
...G-Force\Themes\Your Theme Name\theme.txt
on Windows machines (anyway).
The question is if this action is something local to/implemented as part of the toolbar, or can an equivalent action be preformed as a startup procedure (i.e., for the ScreenSaver)
I CAN NOT find an example/documentation for reading the theme.txt files. Their format (except for the header) is straight forward enough. I would think that this may need to be addressed by Soundspectrum as a trouble report/question.
I do NOT use themes, but when I change them using the Toolbar to one of the one's supplied, and then go check if the config file is ACTIVE(checked) under its respective slideshow list, FOR ME, things seem copacetic ... not true for you? It also seems to retain the theme, upon subsequent Standalone invocations, so just MAYBE there is an undocumented 'Pref' available...
Sorry I can't provide better news/answer ...
One more thought, I run on XPro32/sp3 and have the task manager opened all of the time. MANY MANY times, the Standalone executable and/or the ToolBar do NOT experience timely deaths and I have to use the task manager to finsh them off. If rouge zombie processes exist, I sometimes experience unpredictable behavior from subsequent Standalone/Toolbar invocations. I am NOT sure how this applies to the Mac, but in the UNIX world 'kill -9' would do the trick!
ScreenSaver Issue Update
I found THIS:
The Preferences File
The G-Force preferences file is a "config" file, meaning it’s a plain-text file simply containing a list of values (in no particular order). Its file format is intended to be learned extremely quickly; the format is described in the config programming section. The purpose of the preferences file is to allow various user variables (ex, window position, full screen resolution, visual reactivity settings) to persist from each time G-Force is run to the next. Since G-Force only writes/updates its preferences file when it exits, you must run and exit G-Force at least once before you (or the ScreenSaver, hmmm??) will be able find it. On Windows, preference files are located in C:\Documents and Settings\Application Data\SoundSpectrum\G-Force" and on Mac OS X, they are located in "~/Library/Preferences/SoundSpectrum/G-Force".
D:\Documents and Settings\Jerohm\Application Data\SoundSpectrum\G-Force\Toolbar Preferences.txt :
:
Theme.Name = "Black Background ColorMaps"
:
doesn't look TOO Promising ... I would bet it is implemented in the Toolbar and NOT accessed by the Screensaver
However, in the same directory are these three files:
'Disabled WaveShapes.txt'
'Disabled FlowFields.txt'
'Disabled ColorMaps.txt'
which contain 'theme-ish' info about the LAST invocation. When MY screensaver starts up, it seems to run in the same state as I last left it in when exitting Standalone Mode. Seek out these files and take a look. (I AM running the Beta however).
What I am thinking is that BOTH your issues are related. Get comfortable that you can set the Standalone/Toolbar themes ... and they should carry over when the screensaver starts up.... just talking to myself.