Two problems introduced by Update 5

[tonyw]

For what it's worth, I just tried to reproduce the problem on my A1-XE using my "Clean Update 5" partition, and it makes no difference to Multiview or the console whether Prefs/GUI/Options/Refresh is set to "Simple" or "Smart". It works normally in both cases, using all applications.

I suggest, therefore, that there must be some other trigger in your system that stops it working. You would have to revert to a clean installation, retest that, then add your customisation until it fails, to find out what is causing it.

[Belxjander]

For what it's worth, I just tried to reproduce the problem on my A1-XE using my "Clean Update 5" partition, and it makes no difference to Multiview or the console whether Prefs/GUI/Options/Refresh is set to "Simple" or "Smart". It works normally in both cases, using all applications.

I suggest, therefore, that there must be some other trigger in your system that stops it working. You would have to revert to a clean installation, retest that, then add your customisation until it fails, to find out what is causing it.

I just tried testing a raw update 5 and my customized setups and both showed this same issue

just for reference my Reservation install is only changed from factory default for the screen mode used

This is on a sam440-Flex

[tonyw]

How very curious. I'll have to try all the other platforms.

[saimo]

For what it's worth, I just tried to reproduce the problem on my A1-XE using my "Clean Update 5" partition, and it makes no difference to Multiview or the console whether Prefs/GUI/Options/Refresh is set to "Simple" or "Smart". It works normally in both cases, using all applications.

I suggest, therefore, that there must be some other trigger in your system that stops it working. You would have to revert to a clean installation, retest that, then add your customisation until it fails, to find out what is causing it.

Well, given that a betatester and another user have reported the same problem, it means that it's not specific to my system, so I'll avoid going through such a painful process - sorry, I just don't have the time.

Regarding MultiView, please note that, as already reported, marking does not work even after booting without startup sequence (whereas the shell works fine): this means that the problem is either in the Kickstart modules or in the application itself. Maybe my MultiView isn't up-to-date? It's version 53.3 (15-Jul-2010) here. If not, it would be cool if you (or anybody else) could suggest me which update the most recent version is included in.

A couple of notes to everybody regarding smart refresh:
* MUI has its own setting for that as well;
* when compositing is on, probably the system avoids sending refresh signals to applications; however, to err on the safe side, it's better to ensure that smart refresh is disabled everywhere (wild guess: maybe this saves the allocation of extra buffers at the creation/resizing of windows?).

[nbache]

Regarding MultiView, please note that, as already reported, marking does not work even after booting without startup sequence (whereas the shell works fine): this means that the problem is either in the Kickstart modules or in the application itself. Maybe my MultiView isn't up-to-date? It's version 53.3 (15-Jul-2010) here. If not, it would be cool if you (or anybody else) could suggest me which update the most recent version is included in.

Multiview itself is (probably) irrelevant, it only acts as a hollow container for loading the actual datatype, such as amigaguide.datatype or text.datatype, based on the file content. All of the functionality, including cut and paste, is in the datatype. What kind of file are you trying to mark stuff in?

Best regards,

Niels

[tonyw]

If marking fails, regardless of which application, on your clean installation, then there must be a difference between your "clean installation" and mine. The only possible difference that I can think of is Locale/Input settings. These are carried over from Update 1's original installation.

So what Locale langauge, timezone and keyboard settings have you set?

[Belxjander]

If marking fails, regardless of which application, on your clean installation, then there must be a difference between your "clean installation" and mine. The only possible difference that I can think of is Locale/Input settings. These are carried over from Update 1's original installation.

So what Locale langauge, timezone and keyboard settings have you set?

For my system that would be "New Zealand " and "Japan " as separate tests

I am testing perception against Japanese to try and get functioning Input and display happening by using a fresh build for every test

[Belxjander]

If marking fails, regardless of which application, on your clean installation, then there must be a difference between your "clean installation" and mine. The only possible difference that I can think of is Locale/Input settings. These are carried over from Update 1's original installation.

So what Locale langauge, timezone and keyboard settings have you set?

English language with "New Zealand" and "Japan " as the country settings

Using my custom setup and also testing perception-ime as another option


I have also got an issue with TrueType fonts that I am debugging
I think its also Why I have TimberWolf stalled at its banner window

[saimo]

Multiview itself is (probably) irrelevant, it only acts as a hollow container for loading the actual datatype, such as amigaguide.datatype or text.datatype, based on the file content. All of the functionality, including cut and paste, is in the datatype.

I guess the graphical rendering isn't included, right?

What kind of file are you trying to mark stuff in?

Plain text.

[saimo]

So what Locale langauge, timezone and keyboard settings have you set?

I made the tests with no Locale settings at all (i.e. no ENVARC:Sys/Locale.prefs, ENV:Sys/Locale.prefs and SYS:Locale directory) and with this configuration:
* Language: none (i.e. built-in English)
* Country: Italy
* Timezone: Italy

I've tried both cases with the Italian keyboard setting and the no-Locale case also with the built-in keyboard (American). The results are identical (i.e. no marking).

Anyway, MultiView is no issue to me, but I'm really concerned about the make problem, which seems to have passed unobserved.
In the meanwhile, I've found that the problem is even easier to reproduce and more troublesome that I thought at first. F.ex. while the simple makefile below is processed, those annoying 1-2 seconds pauses happen in several places (which might differ from time to time).

Code: Select all

test:
	Dir RAM:
	Dir RAM:
	Dir RAM:
	Dir RAM:
	Dir RAM:
	Dir RAM: