I will try to clarify some issue with colors & fonts
1. I start the editor, all colors and fonts are as I want them to be.
2. I decide to change a color say the background color of the comment's.
3. I open the colors & fonts window.
4. It opens showing the fore and background color for default they are both white but when i closed them the foreground color was white and the background color was black.
3. I ignore this (for now) and go to the setting for comments I change the background color and click on the apply button.
4. What happens is that the background color for comments is changed into the set color AND ALSO THE DEFAULT BACKGROUND COLOR IS SET TO WHITE.
5. If I understand what you wrote about the apply button this should not be happening.
After this first time the apply button works as you described it.
So there a two thing every time I open the colors & fonts window the default background color is changed. I need to set it every time to the color I want. When the apply button is used the first time it seem not to work as it should.
The things is that when the file gets compiled success full I do not need to see all the information regarding the compiling process only a short message like "MAKE DONE" or simply "OK" would be enough. If something go wrong then you get automatically a output with error messages. The -v option gives more information about what compiler is doing. When all goes well I find that information useless.marpon wrote: Compiler Results
I think -v has to be used if you ask for log , if not you can miss information if something wrong !
you can skip the dialog with the option (not when error) , but to get 1 dialog just to see its ok ???
what difference with the complete log file : only 1 click to do
I haven't done much computing the last week but i have played with it and found a few thingsmarpon wrote: Nota: no remarks on the lynx tool for projects ?
I have collected them in a litte bas file.
Code: Select all
' LYNX process this things incorrectly
/'
dim as byte arr(0 to 7) = {1, 2, 4, 8, 16, 32, 64, 128}
dim as byte arr2()
redim arr2(100)
arr2(1) = 1
arr2(2) = 2
ReDim Preserve arr2(2)
'/
type str1 as string ' has no END TYPE lynx can't handle it
dim q as integer
dim as integer q1
q = 1
q1 = 10
q = q + q1
print q
sleep
end
A comment block does not need to processed it is not included in the code so information gained from it is worthless.
2. LYNX processes data. (get confused by {}).
In dim as byte arr(0 to 7) = {1, 2, 4, 8, 16, 32, 64, 128}, {1, 2, 4, 8, 16, 32, 64, 128} is just data for the array arr(). (arr(0) = 1, arr(1)=2, ... arr(7)=128).
3. LYNX has trouble with REDIM.
It show the array name with a red diamond it should ignore array names that are REDIMed.
4. LYNX get confused by a single line defined TYPE.
It is possible for FB to have a single line defined TYPE without a END TYPE.
LYNX processes all the lines to the END statement as if the where part of the TYPE definition.
That all for now. If you need more information let me know.
Regards