Rainmeter Forums

smurfier wrote:I prefer highlighting valid values. With how key names highlight when valid, it just makes sense that the values should follow the same rule.

However, because only string options (i.e. Hidden=4 is considered valid) are highlighted (for now), I think highlighting when invalid makes more sense and also looks a tad cleaner:



(I'll probably add a dialog to change options such as this sometime in the future)

I'm against adding the equals sign. It seems like it might save the quarter of a second that it would take to type it, but I know there are a lot of people that like to make their skins readable by tabbing the equals signs or otherwise spacing them.

As for the highlighting, could you do both? Have a "correct" colour and an "incorrect" colour. Mind you, I think the best thing for incorrect would be a strikethrough. That would make it obvious.

Alex2539 wrote:I'm against adding the equals sign. It seems like it might save the quarter of a second that it would take to type it, but I know there are a lot of people that like to make their skins readable by tabbing the equals signs or otherwise spacing them.

That wouldn't work as leading/trailing spaces are considered part of the word (but fixed it already, thanks). I'll just include both

Alex2539 wrote:As for the highlighting, could you do both? Have a "correct" colour and an "incorrect" colour

Yep, I'll do that. Strikethrough is not possible with Notepad++ as far as I know, unfortunately.

RainLexer 0.9.1 is out, read first post for download link and instructions.

Changes from 0.9.0:
- ADDED: Seperate highlighting for internal variables (such as #SKINSPATH#) and external variables (such as #MyVar#)
- ADDED: Highlighting for the equals sign in Keyword=Value
- ADDED: Highlighting for valid and invalid values (in cases such as StringCase=UPPER/LOWER/etc.)
- ADDED: Auto-complete (optional)
- FIXED: Leading and trailing whitespace was not ignored (e.g. Active<tab><tab>=1 was not highlighted)
- FIXED: Special keywords like MeasureNameN and ScaleN are now highlighted
- Moved keywords out of the .dll and into the .xml file
- Improved logic and performance

For the next version, I plan on including calltips (a tooltip that shows valid options for keywords) and perhaps operator (e.g. +, ?, /, etc.) highlighting as well.

Outstanding! I'm in middle of getting my two new 1tb hard drives up and configured, but will try it out in just a few minutes.

You may have already caught this, but I notice these anomalies with #VariableName#:

By the way, I was not convinced I would like "auto complete", but I was wrong. It's GREAT!

This is too cool for school, poiru...

RainLexer 0.9.2 is out, download link in first post.

Changes from 0.9.1:
- FIXED: Variables and bangs were not highlighted if the keyword was invalid
- FIXED: Highlighting was not applied completely for lines longer than 2048 characters
- FIXED: Highlighting was not applied correctly for the last line of the file
- Rewrote lexer logic for better speed

Seems to have fixed it poiru...

RainLexer 0.9.3 is out! Now includes and installer so installation is a breeze. It also keeps your current colours if you're on a recent-enough version (that's either 0.9.2 or 0.9.1).

Note that auto-complete must be installed manually (for now). Read first post for download link and instructions.

Changelog:
- FIXED: Highlighting files in Unix format (newlines)
- FIXED: Variables or bangs longer than 30 characters cause crash
- FIXED: Section highlighting when section name has a space
- FIXED: Option highlighting with leading whitespace.
- FIXED: Bangs and variables in the value weren't highlighted when the keyword had non-alphanumeric characters.
- FIXED: ## was highlighted
- ADDED: Installer for easy installation
- Minor tweaks here and there