Perhaps having a style in the highlighting set-up called “Default” and using that across the board where situations aren’t defined might be more consistent. A bit like CSS and inheritance from a top level ancestor style.
No problem. Any other inconsistencies you notice just pass them along.
On 10/02/2013 12:50 PM, PaulZip wrote:
Reply by PaulZip
Thanks Michael. I don't mind if the colouring only applies to the main edit control, as long as it is consistent and other editor parts of TOAD don't partially use this colour scheme (like font colours but not background). My main gripe is not being able
to see text in controls, rendering them not very useful, or inconsistencies on when it does and doesn't apply.
I look forward to the next version and many thanks for finding time to answer.
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Or
Unsubscribe from Toad for Oracle - General notifications altogether.Toad for Oracle - Discussion Forum
Flag
this post as spam/abuse.
Highlighting is done using a lexer. The lexers are specific to the editor component used in the editor and in some other areas of the product. Only editor controls that assign a lexer to them will use those settings. The editor font
option in View|Options|Editor|Display sets the font of the "Default" style in each lexer. There is actually a style named "Default" just as you suggest only it's hidden from you since it is altered by that option. The background color option should apply to
all editor controls that assign a lexer. Since all lexers obey the font setting all editor controls using a lexer should obey the background color as well. It's similar to a CSS as you mention, but just like a CSS the lexers do not have to be implemented by
every editor component. Also, not every edit component you see in Toad is the editor component capable of utilizing a lexer.
Since the emails earlier I've identified a few more places where background color/font color clashes can occur. I'm trying to get them knocked out as I go.
Michael
On 10/02/2013 12:53 PM, PaulZip wrote:
Reply by PaulZip
Perhaps having a style in the highlighting set-up called "Default" and using that across the board where situations aren't defined might be more consistent. A bit like CSS and inheritance from a top level ancestor style.
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Or
Unsubscribe from Toad for Oracle - General notifications altogether.Toad for Oracle - Discussion Forum
Flag
this post as spam/abuse.
I’ve been trying out the new beta (12.5.0.3) and noticed some of the editors have had the syntax highlighting issue fixed. However I noticed another place still not fixed : Parameter prompt form for when you run a query with parameters.