Welcome Guest. Please Login or Register. Apr 1st, 2018, 03:58am
ATTENTION MEMBERS: Conforums will be closing it doors and discontinuing its service on April 15, 2018. We apologize Conforums does not have any export functions to migrate data. Ad-Free has been deactivated. Outstanding Ad-Free credits will be reimbursed to respective payment methods.
Thank you Conforums members.
Speed up Liberty BASIC programs by up to ten times!
Compile Liberty BASIC programs to compact, standalone executables!
Overcome many of Liberty BASIC's bugs and limitations!
Re: Limitations of Syntax Coloring
« Reply #41 on: Dec 13th, 2017, 2:41pm »
Although I have been using LBB for quite a long time now, I have only just discovered that the syntax colouring problem manifests itself in the same way when LBB is run with linux/wine. My language setting is English-UK and many fonts tried. My programs do not contain any foreign characters. Whether that helps or not I don't know, but I am not expecting a solution - I can live without colouring as I obviously have done for some time! Just thought I would add to the gathered knowledge.
I have only just discovered that the syntax colouring problem manifests itself in the same way when LBB is run with linux/wine.
You refer to "the syntax colouring problem" as if it is something well-known and common, but the 'problem' discussed in the earlier posts of this thread manifests only in very rare circumstances, as I have explained. I should perhaps delete those posts in which the issue was misunderstood and misrepresented.
To reiterate, it occurs only when Windows performs a 'font substitution', which can happen when your program contains a character that is not available in the currently selected font. You can often avoid it altogether by selecting a font with a wide coverage of Unicode glyphs (don't choose 'FixedSys' which is particularly poor in this respect; note the reference to 'FixedSys Excelsior' as a possible alternative).
There is nothing I can do about the rare occasions when it does misbehave, because the Rich Edit control does not notify the host program that a font substitution has taken place.
Syntax coloring works perfectly for me, and for most other users as far as I know.
Logged
