change font for ASK buttons

billworld · Post by **billworld** » Wed Nov 26, 2008 4:59 am

Yet another inconsistency with RR...

The font for the "Cancel" and "OK" buttons doing an ASK command are different than those used for the buttons in an ANSWER command. Looks sloppy...

How do I fix this? The ASK buttons font is off.

Also, the horiz. alignment between the text in the ASK statement and the left edge of the text input is off. This is such basic stuff. Yes, I know I can just create my own dialog cards for this stuff, but, this environment was supposed to make everything much easier/faster...

Janschenkel · Post by **Janschenkel** » Wed Nov 26, 2008 8:21 am

The buttons are designed to "inherit" the system font, but it looks like someone accidentally set the 'textFont' property of the "Ask dialog" stack to "MS Sans Serif".

Please report this issue using the Quality Center so it can be fixed for the next release.

TIA,

Jan Schenkel.

billworld · Post by **billworld** » Wed Nov 26, 2008 4:08 pm

Not to sound too negative, but, I've spent the time to file over 18 reports in my very short time using RR, they all still have a status of "unconfirmed". Doesn't really build much confidence that all the time spent documented problems are actually being heard.

Anyway, I'll go ahead and log this one as well...

Janschenkel wrote:The buttons are designed to "inherit" the system font, but it looks like someone accidentally set the 'textFont' property of the "Ask dialog" stack to "MS Sans Serif".

Please report this issue using the Quality Center so it can be fixed for the next release.

TIA,

Jan Schenkel.

Janschenkel · Post by **Janschenkel** » Wed Nov 26, 2008 8:03 pm

Unfortunately, the team doesn't always update the Quality database right away - I know of a number of bugs that have actually been solved in recent versions, but haven't been closed yet by the team.
They also tend to fix a good number of bugs with every release, giving higher precedence to crashing bugs while balancing the bug-fix time with the development of new features.
But it would be nice if at least they went through it twice a week to say "yeah, this is an error that I can reproduce" or "hmm, I have no idea how I can reproduce this, can you help me find a good recipe?"
Then again, I'd rather have them squish the bugs and build new features than keep all the paperwork done

Jan Schenkel.