I should have paid more attention - dark mode in beta since LAST summer! NICE

My sentiments exactly! Sorely missing feature of many apps still unfortunately. I'll be sure to keep beta checks on in LogFusion from now on.

OK so now the complaints (issues?) begin
Hovering over a "highlighted" line, from the highlight settings which I use heaps and is a great feature - say with yellow background highlight in the log in dark mode - it's not so good. Highlight line/text both go pretty much to black and you can't see them no matter what background/text colors you choose.

Edit: actually editing the text color of a highlight rule doesn't seem to save it.

Took me a minute to understand the scenario, but I see it. I mostly use a dark blue background with bright white text. I'd forgotton about the highlight feature and now will start using it again, indeed very handy.
But adding an entry to highlight something then setting it to yellow background with black text --- then hovering over that highlighted line does make it unreadable. Not sure how much pain devs have to go through to manage scenarios like this where the user is allowed to change foreground and background colors for things. The hover highlight would need to examine the color and KNOW that the hover color attributes would need to change dynamically to adapt to the color settings in use.

Edit: changing text color of highlight DOES work for me also

Also, what's the purpose of the "test string" under Highlight Testing? My guess is that it would render in the colors chosen?

Ok, I see the test string purpose - to aid with syntax when deriving a match string.

But, though I've setup on match string that works fine, setting up a second one just as simple does not work at all.

Don't have it handy in front of me right now, but the issue for me is that I have say a yellow background / white text highlight, or anything really, and when hovering the mouse over one of those lines the line goes to basically black on black so you cant see the line/text at all (or very close to it). There does not seem to be a way to change the hover color settings?

My yellow(back) and white(text) work OK. But if text is changed to black in the highlight rule then I see the issue.

OK sorry, that was my bad, the log window I had at the bottom of the screen and the (really slow to open) settings window because of it's large size opened with the OK/Cancel/Apply portion off screen, I wasn't OK'ing the color change because of that. Maybe some kind of force the window onscreen check could be useful - but no big deal?

Any thoughts on why my 2nd rule doesn't color items in red?

https://www.logfusion.ca/Discussions/View/logfusion-67-now-available/?ID=3cf28c0f-5c32-45ac-82b0-9d344c3bea54#9

Not me, I made two similar rules and they both appear to work.

Here's the settings in the Edit window...

Here's the settings for the other rule - the first one I added - that does work.

I think it already centers over the main window, however if the main window is bottom of the screen or bottom right for example, and very small (in this example it's minimum size), the settings window opens partially off-screen.

If the log window is top of screen, Windows automatically takes care of shunting the dialog window into screen view, at least vertically.

I guess it's up to you if you want to add the extra check/move code when a dialog is opened. This is standard Windows behaviour, so it's not a bug per se. It can just be inconvenient making the user move the dialog back on screen to use the OK button. Caught me off guard because in my earlier post only the OK/Cancel/Apply button portion was off screen and I and forgot they were there and used the close button thinking that it would apply the changes (Mac preferences style).

I'll try that, but why does the other expression work as expected?
*edit*
Did not make any difference. I also tried removing all the words except for error, still would not highilght the entry with 'error' in the message.
The message for this particular event ia rather long. Is there an internal limit on your parser scanning those fields? It's 1,436 chars.

I added a few more random highlights and they do work. Must be something about this one.

No. It only shows highlighted lines for 3 of the 4 rules defined. The rule colored red that I have since changed to a single word, error, is not shown.

Highlight dropdown menu?

That's it !!!

How on earth did that ONE happen to be "disabled"? I've never viewed that dropdown menu before but the reason THAT particular highlight was not being displayed was VERY clear once I saw the dropdown.

Thanks!

It would be nice. I tend to hang the main log window over Visual Studio on the bottom right of the VS Debug Output window that I have there. It's convenient to save screen space when "drilling deeper" into the debug log. If I need to change settings the (massive!) settings window opens partially off screen as I've said.
I have code to shunt windows on screen in a multi-screen environment in situations like this that I use for my projects if you want to DM me and check it out.
edit: Also, a suggestion when in dark mode and adding a new highlight, perhaps swap the back and text colours?

Yes I got that already and seems good. Thanks.