In my Xojo, I set the Code Editor to use a monospaced file, Courier.
Here, there and everywhere, I use headings like this one:
// ********** ********** ********** ********** ********** ********** ********** **********
//
// Menu: File
// MenuItem: CSV
// SubMenuItem: Import
//
// Let the user choose (or not) a csv file and open / display its contents.
//
// Line 1 holds the Heading Strings
//
// [2015-09-28] Removed the CSV suffix from the Menu Handler.
// [2016-06-09] New added feature: Populates the Recent Menu
// [2016-07-09] Takes the Method code that deals with loading CSV back here
//
// ********** ********** ********** ********** ********** ********** ********** **********
//
Nota: the leading spaces (before the “//” comments are set by Xojo at Copy code time.
This is just an example.
Now the question:
I understand why one want to remove useless (and invisibles) spaces, but in the case above, it will be against my own will / way of presenting stuff / clearity.
What is the Xojo developer (user) have to understand in this business to remove all spaces (nearly) in Xojo Code ?
If the reason is good enough, Xojo have to remove spaces before the open/close parenthesis (some people adds), between the asterisks (above), etc., after the separation comma of Methods / Functions Parameters, etc. (unless if this is already done and I do not saw that.)