Code::Blocks Forums
Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: duncanka on January 06, 2006, 07:53:12 am
-
Just wondering...
Is there some particular reason why the "Find"/"Find in Files" dialog has three different radioboxes of options all labelled "Radiobox"? Shouldn't those have more descriptive names, like "Scope" and "Search context" and "Direction"?
Also, though much less importantly - shouldn't the "OK" button in the Compiler options dialog be capitalized?
Not big issues, but these labels do seem a little unprofessional...
-
hey I never noticed this, wonder how long that's already there.
@Yiannis : now there's a big bug challenge for you ;-)
-
The labels apparently got lost in revision 1583. Since there is no label at all, it shows the default, "Radiobox".
The more interesting question is why nobody noticed that until today :lol:
The "Ok" buttong in the compiler dialog looks like in all other dialogs, so we would have to change them all if "Ok" should really be capitalised (I'd not do that for consistency).
-
The labels apparently got lost in revision 1583. Since there is no label at all, it shows the default, "Radiobox".
The more interesting question is why nobody noticed that until today :lol:
I don't know about others, but I usually look at the options themselves, not the label of the containing frame.
The "Ok" buttong in the compiler dialog looks like in all other dialogs, so we would have to change them all if "Ok" should really be capitalised (I'd not do that for consistency).
Actually, all the other dialogs in the settings menu use "OK" (or "Close", which can also be seen as an inconsistancy).
Project Properties also has "OK". I can't find any other dialog that uses "Ok" on a quick check though...
-
Actually, all the other dialogs in the settings menu use "OK" (or "Close", which can also be seen as an inconsistancy).
I 'd say it's a matter of culture (at least for me ;)), if "OK" should use both capital letters.
Ola Kala (Greek: Everything's fine; an origin for the word Okay)
In Greece teachers would mark especially good school papers with "OK" for Ola Kala (Ολα Καλά, ΟΚ), meaning that everything is good; as a variant on that story, the Greek phrase would be used by sailors as a quick way of responding to the captain's inquiry about the condition of the ship. O.K. was marked on shipping crates after inspection, as the crates travelled and disembarked around the world people saw the abreviation as meaing everything in them was all right 'Ola Kala'.
(source: wikipedia (http://en.wikipedia.org/wiki/Oll_korrect#Greek_Language))
Anyway, in most places of the world, OK is an acronym and as you know acronyms are written with capitals so that answers your question on how it should be written :).
(I bet you never thought that way about OK before :P).
-
Isn't "Kimono" a Greek word, too?
-
Isn't "Kimono" a Greek word, too?
You know it is :lol:
As for the origin of OK there are many different explanations but I was also raised with Yiannis' version so it's kind of hard to interpret OK in any other way than "Ολα Καλα" (all other explanations are also kind of boring :)). And to stay on topic I also always use the capital version of OK.
-
The labels apparently got lost in revision 1583. Since there is no label at all, it shows the default, "Radiobox"...
was skiing the last weekend - if not already done, i'll fix this soon
i edited the dialog resource xrc file with DialogBlocks V2.04 and obviously the radiobox labels got lost during import / export with Dialogblocks :shock: - sorry for that .
is there any other program which is supposed to be used for editing Codeblocks' dialog resources ?
-
this is still the case in latest svn : both on the find and in the find in files tab
is there any other program which is supposed to be used for editing Codeblocks' dialog resources ?
notepad ? vi ? .....
-
is there any other program which is supposed to be used for editing Codeblocks' dialog resources ?
I 'm using XRCed...
-
I don't know if y'all have noticed, but the .xrc files in the project have a VERY large number of blank lines with trailing spaces. I'd estimate a 50+% filesize savings across all of them if the trailing spaces were removed...
-
I don't know if y'all have noticed, but the .xrc files in the project have a VERY large number of blank lines with trailing spaces. I'd estimate a 50+% filesize savings across all of them if the trailing spaces were removed...
I don't think so, Sam.
src/dlg_about_plugin.xrc has a few such lines.
sdk/configure_tools.xrc has a few such lines.
All other files do not.
It matters very little alltogether, since these files are zip compressed anyway, and we are currently more interested in readability than in file size.