My First Glance At 3.5.1...Yay

[JayPro]

I'm doing some major testing on this and I wish to offer these few starting words.

1. The V-Bar, as beautiful as it is, slows down to varying degrees depending on which tiling mode is chosen.

2. Some of the items on my configs lists show blanks and I don't now why. I try to activate them and nothing seems to happen.

3. Major Annoyance If I May Be So Bold:
***Right Out with the "Next (Insert Config Name Here)" Text!***

I almost had a heart attack or three looking at flowflelds that I know are supposed to work a certain way and freaking out, only when the false behavior I thought I saw was due to the Next FlowField text showing up concurrently with what was in fact on-screen at the moment.

And it doesn't help matters when both the size of the console fontage and the font itself are set in stone to outputs that I can hardly see.
I'll say this again and hope against all hope that it soon gets addressed:
There Just Has To Be A Way To Add Two Simple Params To The BootFile/PrefsFile: One For Adjusting Console Font Size And One For Adjusting Console Font.

I utterly fail see why this cannot be done despite all the advances we've made on this. I pray you forgive my apparent indignation here; but my reasons for harping on this go far beyond my personal distaste for the size 12/14 Monaco font...or the font aforementioned at *any* size. This is the console font on my iMac BTW. It may be different for Windows users; but that's not my point.

The "boldness" (pun intended) of my plea can be "underscored" (ditto) by the fact that some, or even many, GF users could have visual impediments of many sorts; and the way things look IMO may not even be viewable by them.

4. The Toolbar quits when it gets overly tweaked. Maybe the fault is mine since I tend to noodle around with things at a fast pace.

5. I may hafta flag down certain effects that call for tweakings in the updated syntax and send them to a few willing persons for fixing up in that regard. E.g. I can deal with when VectorC calls for a fill-in of a missing parenthesis; but I'll definitely need help with the float() things and such.
Strangely enough, though, even though one of my waves (Tudor Park) gets "outed" by the VectorC compiler for (IIRC) a missing float value, the effect itself appears exactly as it should. This is at once most reassuring and something that flies in the face, apparently, of the compiling inaccuracies cited.

Otherwise, the interface is most attractive and satisfyingly intuitive. I also appreciate the wealth of features presented.

Back to testing

[andy55]

1. The V-Bar, as beautiful as it is, slows down to varying degrees depending on which tiling mode is chosen.

What machine are you running on? The CPU needed for multiple G-Force tiles is what it is, unfortunately.

2. Some of the items on my configs lists show blanks and I don't now why. I try to activate them and nothing seems to happen.

Do you have an active sound source selected? If you're imputting from, say, the mic you're not going to see anything for most WaveShapes.

3. Major Annoyance If I May Be So Bold:
***Right Out with the "Next (Insert Config Name Here)" Text!***

I almost had a heart attack or three looking at flowflelds that I know are supposed to work a certain way and freaking out, only when the false behavior I thought I saw was due to the Next FlowField text showing up concurrently with what was in fact on-screen at the moment.

And it doesn't help matters when both the size of the console fontage and the font itself are set in stone to outputs that I can hardly see.
I'll say this again and hope against all hope that it soon gets addressed:
There Just Has To Be A Way To Add Two Simple Params To The BootFile/PrefsFile: One For Adjusting Console Font Size And One For Adjusting Console Font.

I'm not totally sure I understand your problem. As for your console text appearance comments, keep in mind 95%+ of people never use or see the console (and don't care to see it). The console is intended purely for error reporting and config developer use--it's not expected that you'd ever want to see console text in the V-Bar. A conifg author would use standalone or a media player to develep a config or script. Given it may be hard to read 9pt text, I'm sorry--perhaps I can add the size change in the future.

4. The Toolbar quits when it gets overly tweaked. Maybe the fault is mine since I tend to noodle around with things at a fast pace.

Um, please report that. I can't fix crashes that I don't know about. Please copy and paste me all crash report text.

5. I may hafta flag down certain effects that call for tweakings in the updated syntax and send them to a few willing persons for fixing up in that regard. E.g. I can deal with when VectorC calls for a fill-in of a missing parenthesis; but I'll definitely need help with the float() things and such.
Strangely enough, though, even though one of my waves (Tudor Park) gets "outed" by the VectorC compiler for (IIRC) a missing float value, the effect itself appears exactly as it should. This is at once most reassuring and something that flies in the face, apparently, of the compiling inaccuracies cited.

If VectorC is reporting an error when there isn't one, please file a bug report.

[willrob]

I think JayPro's comments about the font size were not for the V-Bar, but in a media player. I use iTunes (on a Mac) and find the console difficult to read on my 17 inch monitor. I can read it, but it would be easier to read if I could select a sans serif bold font.

My experiences with the ToolBar have been positive, except for the bug I reported way back when: if I try to select a theme, other than the default, the tool bar will quit a few seconds later. I have no problem selecting anything else; only with the themes. I can select items in the V-Bar prefs without any crashing; although there are no themes there to select.

[andy55]

My experiences with the ToolBar have been positive, except for the bug I reported way back when: if I try to select a theme, other than the default, the tool bar will quit a few seconds later. I have no problem selecting anything else; only with the themes. I can select items in the V-Bar prefs without any crashing; although there are no themes there to select.

If you get a crash, please formally report it and paste the full crash text. I unfortunately am not able to read and check this forum on a consistent basis, so you need to formally report a crash. This is the first time I've heard of this crash (keep in mind that if you emailed me a crash report X weeks ago, I've been wading through and fixing dozen of bugs in the beta, so there's no way for me to know if it got fixed or not). In other words, if its been longer than a week and you've reported a crash in an official, released version, then I haven't seen it yet (and you need to shake my tree harder if you ever want it to get noticed and therefore fixed).

andy

[JayPro]

I was referring to the console text that gets called up by toggling the V key, regardless of media player or standalone.

That said, I realize that almost no one would keep GF running in verbose mode. My concern was that when I needed V-mode on to check for dysfunctioning non-bundled flowfields in my personalized copy, it was difficult to read which was the present flow and which was the one to come up next.

I merely pointed out that the size and resolution of the V-key font was too small IMHO *for the particular purpose in which I was engaged*. Now that I think about it, Andy and company really may not have the time or inclination to futz with the Prefs over a piss-ant detail like the one I cited in the beginning...never mind the possibility that it just might not be feasible.

Bottom line is that I don't really think that the "Next Flow Field" alert is necessary and tends to be rather confusing.

PS: Becuase of my disability I don't have binocular vision like most people. I tend to use one dominant eye when focusing on a particular thing. And sometimes this complicates things a bit for me.

BTW, Andy:

In future, I will keep bug reports consigned to the appropriate means via sending them. I just got carried away in my initial post with some quick, albeit not to-well-thought-out observations.