From: <aji...@t-...> - 2001-11-10 20:59:53
|
The only problem I have found as yet is that the width of the float field does not seem to be influenced by the values entered in the 'Edit List Views' dialog. However I do not think this qualifies as a 'bug'. I am really impressed by the fact that all float values are alligned with the decimal point. GREAT I am also impressed by the fact that in the list field dialog, if the number of items entered exceeds the no of items displayed, the list is automatically scrolled down to the latest entered value. Re. the localised float display: If I enter a value and by mistake have used the wrong decimal point representation, the value I have (wrongly) entered is overwritten by [nan] (not a number) in the list view, and I have to re enter the value again, which, in some cases could be tedious, e.g if I have to look it up again in some table, especially if I have entered many wrong values in many float fields. Scott had said that he wanted to implement it in such a way that you cannot leave the edit view if a non-recognised decimal or character is entered. This makes sense. Let us say the format used is the english format 1,000.00 and one enteres say 123,456 instead of 123.456. If you TRY to leave the edit view, it would be nice if the following pop-up window would appear: 'the syntax in 123,456 is wrong'. Even better would be the recogintion of the wrong decimal representation with a window saying 'wrong decimal syntax' and 'the syntax in 12.a456 is wrong' if 12.a456 is the value entered, i.e. if a character is entered by mistake. This would still give you the chance of going back and just changing the wrong decimal or digit instead of having to enter everything again. However, this is also not a bug by any definition, so in my opinion, this version can be released Once again, what an outstanding piece of software! Hans |