A few trolls here have derided the utility of being able to examine and to modify code. I am not a C-programmer but I am not a complete idiot and can and do examine the source code. I have been using a neat little prgramme, gebc (GNU Exterior Ballistics Computer) but found a couple of rough edges. One of them I could fix…
“On my system, the column heading "Wind Drift" is cut at both ends to "Vind Drif" in the Range Table. I edited the file RangeWindow.cpp to change "Wind Drift" to "Windage" in this (123) line: tbl->add("@b@cRange\t@b@cDrop\t@b@cDrop\t@b@c
Velocity\t@b@cEnergy\t@b@cWindage \t@b@cWindage\t@b@cTime",0); There still appear to be a couple of pixels shaved off the "W" but it is more readable this way. The programme gives me accurate results. I would like to see it improved with resizable windows, fonts, etc. It is very usable as is but my eyes are old…”
see GNU Exterior Ballistics Computer | Reviews for GNU Exterior Ballistics Computer at SourceForge.net.
The programme is easily built with
in the directory gebc-1.07 for the version I have. The download came as a .tar.gz file.
The idea that being able to examine or to modify the source code of software is somehow a disadvantage or useless is silly. Clearly it is an advantage and one that ensures bugs can be squashed more rapidly and by a more diverse group of users.