Comment by
Robin Shen
[
04/Jan/10 11:31 PM
]
|
Can not reproduce this at my side. Would you mind sending your database with detailed steps reproducing this?
Thanks
|
Comment by
Roger Perkins
[
05/Jan/10 03:36 PM
]
|
All I did was create a Config... add a variable.... it's a selection box with two values... first time it prompts for the value it defaults to "empty" and happily lets you select that despite "allow empty" being set to false. If you do pick either of the two values, next time around it shows the previous value, but still populates the drop-down with an "empty" value which it'll happily let you select and click OK to proceed.
|
Comment by
Robin Shen
[
06/Jan/10 12:59 AM
]
|
Run exactly the same steps but still can not get it reproduced. What is your browser? If it can be easily reproduced at your side, can you do the favor of sending the sample database demonstrating the behavior?
Thanks a lot.
Robin
|
Comment by
Roger Perkins
[
20/Jan/10 12:20 PM
]
|
Here's a test configuration. When you run it you should get prompted to select true or false from the drop-down, however you'll also always get an "empty" option in the drop list. You shouldn't be seeing an empty slot and definately shouldn't be allowed to select it when "allow empty" isn't selected.
I've seen this with the server running on Windows x86 and x64 when used in conjunction with IE8, Safari and Chrome.
|
Comment by
Robin Shen
[
21/Jan/10 02:30 AM
]
|
Thanks for sending the sample. I did get it reproduced. QuickBuild has some bug when handling variable names containing upper-case characters. And we will address the issue.
A temporal workaround for now is to change the variable name from "TEST_VAR" to "test_var".
|
Generated at Fri Oct 03 22:27:01 UTC 2025 using JIRA 189.