bustiiing / blazingstars

Automatically exported from code.google.com/p/blazingstars
0 stars 0 forks source link

QA Report on BlazingStars Preferences #28

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
I downloaded BlazingStars-0.9.8b-20.dmg and read thoroughly through each 
preferences panel. Here's my thoughts. Nothing here is 
urgent. Some issues might be debatable. Everything can wait until after 1.0 if 
need be:

On Basic Keys, "Advance Actions" should read "Advanced Actions"

There should be a "Restore Defaults" button, as per Mac OS X 10.6 System 
Preferences -> Keyboard -> Keyboard Shortcuts

On Windows, there should be a preview showing a sample of a box with the 
specified colour, opacity, and width.

On Open:Close, there are two tabs. They are unnecessary. It is better to show 
all options at once in two grouped boxes.

On all panels: Some checkbox texts end in full stops (periods). Some don't. Be 
consistent. What does Apple do in their preference 
panels? I just looked and the  answer is no periods.

In Advanced, the checkboxes are back to front. That is, the checkboxes follow 
the text instead of the text following the checkboxes.

In Advanced, instead of telling people how to open the Speech Panel, add a link 
that says "Speech Preferences..." that opens the OS X 
System Preferences Speech Panel directly. 

Original issue reported on code.google.com by steve.mc...@gmail.com on 15 Jan 2010 at 9:59

GoogleCodeExporter commented 8 years ago
Oh, I'm an idiot. It's "Advance" as in "in the future" and not as in "not 
basic".

Original comment by steve.mc...@gmail.com on 15 Jan 2010 at 8:24

GoogleCodeExporter commented 8 years ago
<laugh> In a very early version I did exactly the same thing. :-)

Thanks for doing a QA review, Steve, I agree with most of what you said.  The 
only
thing I'm not sure about is the Open:Close window.  I put it in there because I 
think
there's a logical division between cash games and tournaments in this instance, 
and I
was looking to leave room for future growth in this area.  I'll have to give 
this one
some thought...

I think I'm going to implement the others, though, and push out a new release 
today
to fix all the bugs I introduced in the last one. <sigh>

Original comment by steven.h...@gmail.com on 15 Jan 2010 at 8:28

GoogleCodeExporter commented 8 years ago

Original comment by steven.h...@gmail.com on 15 Jan 2010 at 8:29

GoogleCodeExporter commented 8 years ago
You consider it depressing that you introduced new bugs...or you can consider 
it nice 
that you have active testers who quickly find the new bugs that inevitably 
sneak in...

 ;-)

Original comment by steve.mc...@gmail.com on 15 Jan 2010 at 8:38

GoogleCodeExporter commented 8 years ago
Okay, I've checked in some code for all of the changes I'm going to address 
except
for the "preview window frame" one.  There is currently a problem with the 
clickable
link in the Speech preferences item - the clickable field is shifted to the 
right of
the actual link text.  I know about this, so please don't submit an issue on 
it;  I'm
waiting on the developer of the DSClickableURLTextField class to see if a fix 
can be
arranged or if I'm going to have to rip that out and do it a different way.

I'm working on the window frame preview right now.

Original comment by steven.h...@gmail.com on 18 Jan 2010 at 8:27

GoogleCodeExporter commented 8 years ago
Okay, the window frame preview is up, the defaults button works, the checkboxes 
are
fixed, I don't think I'm going to ungroup the Open:Close prefs for now, and the 
link
is (mostly) working - I'll fix it when I hear back from that developer.  I'm 
going to
move on to other things for the moment so I can get a working release out to 
people.

Original comment by steven.h...@gmail.com on 18 Jan 2010 at 9:05