Another error encountered...
Used SC3 (paid version / SC3 Ultimate Beta version)
Loaded Cloud Thesaurus ...
***** (another suggestion here... when program comes up with "Select thesaurus" window, and you click OK, it shows a progress bar in THAT window with the message "loading... please wait"... but at the same time, while the progress bar has begun "loading", another window "Choose Language" pops up, with English in DropDownListBox (DDLB) showing English and with buttons OK and Close.
Now, my question is why you need to open this window AFTER the progress bar in the main window has BEGUN... this popup window needs to come up BEFORE the progress bar begins. And only after the user chooses the language and presses OK, then the progress bar (Loading) should begin loading the selected thesaurus... Getting my point?)
anyway, continuing...
I loaded a plain text article...
I clicked the Super Spin...
It opened the SuperSpin window... I tried the
Most Unique option
FIRST and kept the default settings in the window, and hit the Super Spin button...
SC3 came up with spintaxed copy of my original article
THEN,
I clicked the Super Spin
AGAIN...
It opened the SuperSpin window... I tried the
Most Readable option
THIS TIME, and kept the default settings... then hit the Super Spin button...
BUT... the program at this stage produced the error window:
"SpinnerChiefIII encountered a problem...."
Why the error window?
The user, imo, can spin the article this way (most unique option) AND then again that way (most readable option)... what's wrong in doing that? Why the program has to get zapped? It's a GUI program and the programmer needs to know that a user can hit any button... the expert will always try to arrest any internal (programmatic or Windows specific) errors happening and will stop it from crashing the program. That's the idea behind GUI programming, because in GUI, a user action can be anything (click on any button, move away, move into any frame, move into any module (clicking into another menu item), whatever... the programmer MUST take into account so many logical decisions like IFs and ORs... THENs,
and not let program to crash. I understand it's in beta, but need to give you these suggestions nevertheless.
Those errors/crashes must be prevented at all costs.
Another suggestion:
Please add
keyboard shortcuts to some of the common menu items such as OPEN (^O), CLOSE (^W), SAVE (^S), SAVE AS (Shift+^S), NEW (^N), ...using mouse on those menu ribbons alone is a bit PITA...
I think these KB shortcuts are already present and working in SC3: Copy, Paste, Cut, etc...
More problems:
If I click on any menuitem under the Help/Support menu, DeveloperAPI, may be other menus too (not checked them all), the application gives me the "Unhandled exception..." error box.
Interesting this!:
I'm of course using the SC3 Ultimate Beta, but when I click HTML Spin button under the Advanced Functions menu, there is a notification box stating:
"Sorry, beta version can't use this function. Do you want to upgrade?
It is free to try."
So what other upgrade is available when I am already using the Ulti eta version?
And if I click Yes on that window, there is another Unhandled exception window... !!
AND, I observed all those menuitems under this menu section gives the same notification and "unhandled exception" error messages...
All these
MINOR bugs can be arrested at the development stages, before the
beta is given to unknown users and exposed over the internet... these are simple minor clicked event bugs and could have been debuged/tested by any programmer while at the coding stage itself.
I, even as a beta-version tester, wouldn't be comfortable with so many
Unhandled Exception errors, and such simple bugs and crashes... Isn't your programmer taking care of these SIMPLE bugs at the modular and coding stages itself?
Thanks!
