Didn't there used to be a separate Bug report section of the forum for reporting problems with new versions?
I remember documenting this problem when 3.8 first came out, and I see that the bug remains unfixed in 4.2. Nor could I find the Bug Report section of the form to make a simple reference to this problem.
The bug first appeared somewhere around version 3.8 when the functions of the "Red/Green" lights in the ToolBar no longer worked like previous versions. Up to that time, one could click the little light to make it Red on any category (WaveShape, ColorMap, FlowFleid), and then use the arrow keys to cycle to the NEXT config file in alphabetical order.
That functionality is not longer present in ToolBar. The bug is particularly frustrating to those of us who write scripts and who are constantly re-writing configs. I don't know about the rest of you, but I uncheck every config when I get a new version. I don't want anything showing up on the screen without it being deliberately called.
As the Arrows are presently set in 4.2 (and 4.0), there is no difference in their reaction when the light is Green or Red. The arrows cause a cycle between CHECKED BOXES ONLY, regardless of whether the light is Red or Green.
Before, if the Light was Green, you could cycle between Checked Boxes using the Arrows, and if the light was Red, you could simply advance to the next available config in alphabetical order using the Arrows. Made perfect sense and provide some great flexibility.
In the earlier-than-3.8 versions, the Green light also signaled that the clock managed by the ToolBar was in effect, and all Checked configs were in play, and all checked configs could be called using the Arrows. If the light was Red, the TooBar clock was disengaged for that particular element, but one could select the next element in Alphabetical order with the Arrow Key, regardless of whether or not it was checked. This was very handy in programming.
At present, advancing to another config with the Blue drop down box is not as good a solution as the previous versions offered. The Blue drop down box was always available, but using the Arrows with the Red light provided much better with flexibility.
Please bring back the same functionality of the Red/Green lights and the Arrows.
And has anyone tested the Black-Out-Bug that appeared in version 4.0? In StandAlone, if fewer than two FlowField configs were left unchecked, the ToolBar wouldn't repopulate on next boot. This bug was also well documented in the missing Bug Report section of the forum.
And just to make sure the improvements in 4.2 don't go un-recognized, it is true that 4.2 is reacting much smoother than 4.0. And I have tested the .gif compatibility and it works fine. I was hoping it would also run animated gifs (to supplement .mov files), but that would have been too much. All improvements are greatly appreciated.
ToolBar Green/Red/Arrow Bug Remains in 4.2
Moderators: BTT, andy55, b.dwall, juxtiphi
Ok, I've restored the previous behavior where stepping when slideshow disabled stepped alphabetically. It was around 4.0 because of internal changes made it difficult, but I managed to find a way in the name of the G-Force community that I know and love so much. 
GF 4.3 beta will be up soon. We have a cool new feature called 'reflex' audio processing that is basically a sound normalizer, so the visual audio level won't be too 'soft' or strong depending on the genre of music.
GF 4.3 beta will be up soon. We have a cool new feature called 'reflex' audio processing that is basically a sound normalizer, so the visual audio level won't be too 'soft' or strong depending on the genre of music.
Last edited by andy55 on Tue Jun 14, 2011 12:47 pm, edited 1 time in total.
What an exceptional idea!andy55 wrote:
...
GF 4.3 beta will be up soon. We have a cool new feature called 'reflux' audio processing that is basically a sound normalizer, so the visual audio level won't be too 'soft' or strong depending on the genre of music.
... now if there was only a way to shuffle favorite scripts too!?! That would be pretty cool!
... and while we are on a roll, also supporting ". + 0:00" script timing format might make A LOT of sense too
thanks for listening... or not...
Hello Andy
Regards BTT
Hope you will include an option to turn on/off this feature, just in case it's not to every one's liking.We have a cool new feature called 'reflex' audio processing that is basically a sound normalizer, so the visual audio level won't be too 'soft' or strong depending on the genre of music.
Regards BTT