Modified Line Highlight

[dunkers]

I've enabled the modified line highlight and left the default colo(u)r as red. Type a bit and there's a red splodge in the margin. Magic.

I type some more and notice that there are dark red splodges in the margin. Oh, I bet it gets darker and the modification gets older! Er.. no. I've spent some while trying to figure it out, but can't.

Anyway, while experimenting I changed the modified line colour to yellow, and found that this also changes the modified tab text colour! Hmmm... don't think I like this. Logically, I'd expect the margin splodge to be the background colour and the tab text to be the text colour - is it a bug that the background is used for both?

So, back to the splodge... blow me if the yellow splodges turn into dark red splodges again. This has to be something somewhere ignoring the modified line colour setting, aka a real live bug, right?

Which brings me to... what's the preferred method for reporting (alleged or suspected) bugs? A post on here or a quiet email to support?

[Ding Zhaojie]

I don't like the way slickedit indicates the modified file so I made some changes to the file tab bar: the modified file name will be marked with a "*" instead of changing the text color. So I can use some light colors to mark the modified lines.

You can find the macro here: http://community.slickedit.com/index.php?topic=82.0

[dunkers]

That's interesting, thanks. I think I prefer the coloured tab since it's easier to notice.

Ah! I think I see now where the dark red is coming from - it's the inserted line thing. I've yet to see a no-save line coloured line so still trying to make sense of all this
Seems to me any line which is new or changed should be no-save until it's saved, and then it should change to the appropriate inserted or modified colour.

[Dswag89]

Which brings me to... what's the preferred method for reporting (alleged or suspected) bugs? A post on here or a quiet email to support?

Don't know much about the highlighting, but from reading other threads here, I think the preferred method is an e-mail to support.  Developers may pick up on this thread, confirm it, and open one themselves, but if you send something directly to support@slickedit.com, it will be in their database and force them to at least investigate/confirm/deny it as a bug or feature.

Dan

[dunkers]

Ta. Once there's some sort of agreement I'll mail support if they haven't shown up beforehand. Wouldn't want to rub 'em up the wrong way

[dunkers]

The DIY fix:

Lines 505-508 in bufftabs.e

Code: [Select]

_str c=_default_color(CFG_MODIFIED_LINE);
 typeless mc;                             
 parse c with mc . .;                     
 sstabwid.p_ActiveColor = mc;             

The "parse c with " is originally ". mc ." which picks the background colour. The change shown here picks the foreground.