Two problems introduced by Update 5

[tonyw]

I have found a way to reproduce your "failure to highlight" problem in the console, at least. If you have the command line option/tooltype in the Shell icon set to "Smart", then highlighting won't work, regardless of the setting of the GUI option "Screen Refresh".

Note that the console documentation specifically states that this is illegal, it must be SIMPLE refresh.

If you have "Smart" included in the Shell tooltypes, I suggest you remove it entirely (don't just replace it with "Simple").

[Belxjander]

I have found a way to reproduce your "failure to highlight" problem in the console, at least. If you have the command line option/tooltype in the Shell icon set to "Smart", then highlighting won't work, regardless of the setting of the GUI option "Screen Refresh".

Note that the console documentation specifically states that this is illegal, it must be SIMPLE refresh.

If you have "Smart" included in the Shell tooltypes, I suggest you remove it entirely (don't just replace it with "Simple").

Was that set at all and I recall the RKRM as documenting console windows as always simple refresh for some reason

I will check the tooltypes when I have a chance

[saimo]

I have found a way to reproduce your "failure to highlight" problem in the console, at least. If you have the command line option/tooltype in the Shell icon set to "Smart", then highlighting won't work, regardless of the setting of the GUI option "Screen Refresh".

Note that the console documentation specifically states that this is illegal, it must be SIMPLE refresh.

If you have "Smart" included in the Shell tooltypes, I suggest you remove it entirely (don't just replace it with "Simple").

I don't even have the Shell+icon thingie: I open shells with NewCLI
Anyway, that the problem was smart refresh in conjunction with compositing had already been discovered...

As for the other problem, is it safe to revert to the old smartfilesystem kernel module? The pauses during the processing of makefiles are really annoying.

[tonyw]

I don't even have the Shell+icon thingie: I open shells with NewCLI

Please give me an example of the command you use - and from where? An existing Shell?

It's precisely this sort of unusual behaviour that could be causing the issue. If you tell me what's different about your setup, perhaps I can help you find a fix for it.

[saimo]

Please give me an example of the command you use - and from where? An existing Shell?

FWIW, from a script that executes this:

Code: Select all

NewShell "CON:480/700/1000/380/development environment/ICONTITLE %D/CLOSE"

It's precisely this sort of unusual behaviour that could be causing the issue. If you tell me what's different about your setup, perhaps I can help you find a fix for it.

I think you're looking in the wrong direction: we know that the problem lies in the fact that shell shouldn't be smart-refreshed (and you've even found that this is documented). The way a shell is started might make a difference only if it triggers an anti-smart-refresh setting, but that's another story

EDIT: forgot to say that I personally don't need a fix, since I already have it, i.e. disabling smart refresh, which is at best totally useless with compositing. The fix would be instead good for the improvement of the OS in general.

[Belxjander]

I don't even have the Shell+icon thingie: I open shells with NewCLI

Please give me an example of the command you use - and from where? An existing Shell?

It's precisely this sort of unusual behaviour that could be causing the issue. If you tell me what's different about your setup, perhaps I can help you find a fix for it.

Can composition replace smart refresh when a compatible card is present using the existing code as fallback?

[tonyw]

@Saimo:

There are some funny things there that I want to understand. Without access to your machine, I can only guess at why it's happening at all. Remember that it does NOT happen on a clean Update 5 installation, no matter what the GUI setting is (Simple/Smart). It only happens if you start the console (Shell) with "Smart" refresh.

I'm beginning to wonder whether some other component has changed so that if you run a NewShell command with the GUI setting of "Smart", it opens the console window in Smart refresh (but Update 4 didn't). If you just open a Shell from the icon it doesn't, but there might be a difference if you run it from a script.

I'll keep looking as and when I get the time. Right now I'm spending most of my time trying to fix my *@#$% gearbox. The campervan has been off the road now for two months...

[saimo]

@Saimo:

There are some funny things there that I want to understand. Without access to your machine, I can only guess at why it's happening at all. Remember that it does NOT happen on a clean Update 5 installation, no matter what the GUI setting is (Simple/Smart). It only happens if you start the console (Shell) with "Smart" refresh.

If you want, I can give you a full copy of my installation. Just send me an email to simone retream com and I'll provide you with a download link in 1 or 2 days.

I'll keep looking as and when I get the time. Right now I'm spending most of my time trying to fix my *@#$% gearbox. The campervan has been off the road now for two months...

I hope for you that you enjoy fiddling with mechanical stuff, otherwise it's a pain...

[ssolie]

As for the other problem, is it safe to revert to the old smartfilesystem kernel module?

It is not safe to revert that component.

[saimo]

It is not safe to revert that component.

OK, thanks for letting me know.