@paolone:

Sorry if i mess up your release schedule -> it is/was not intended... I personaly am not in a hurry here :rasta:.

The haste i had/have is in finding the cause of the problem and at that i failed

Quote:
Just drop me a pm if i can help here (Only virtualbox atm though).

regards,

P.S. i just saw the pubscreen option being added to multiview by georg :thankugeorge: (how the h*ll did that even worked before ?!)

I'm more oriented for a pseudo 1.3.4 update which includes ALL the patches and newer files that will hopefully fix the issue. Since I am working for weeks on a brand new release of Icaros, I think I will call it "patch 05". It will include all news from older patches. I just need some time for making it (and someone testing it on his 1.3.3 installation).

Quote:

That is a question easier asked than answered

Under normal circumstances one would be able to replace individual files (libraries for example) as was done on the original AOS (as it is/was a stable released OS).

With AROS (being a constantly updated OS in alpha status) this is not so easily done. I could for instance replace dos.library (which is most probably related to the issue) but this library on itself depends on an updated exec.library and so on. This is f.e. also why patch 03 updates so many individual files -> they all depend on and/or are related to eachother and needed to be updated all at once.

Poking into this (dependency) system without knowing 100% exactly sure what you are doing is a no-no. Thats why maintainers of distributions are important -> they seem to know what they are doing (and i am not)

The best thing to do imho is A) do not run the patch that is causing the problems or B) wait for another update for the distribution.

I honestly wish i had better news to tell you.

If you really want to revert back in the patches and are unable todo so yourself, then i am more then willing to provide you with the files that need to be replaced in order to revert the patch that is causing the problems for you (but i cannot give a 100% guarantee that it will work).

Ofcourse somebody else might have a better answer/solution for you right now.

P.S. You could always try to bribe persuade paolone (by donating) into making a (quicker released) patch to solve this issue

regards,

So, which files do I need to update for Dopus fix?

Quote:

Quote:

Normally i do too Due to circumstances i used the console mostly for my needs the last couple of months :-S
It is also why i got (a little) upset towards myself also, -> under normal conditions i would have noticed this kind of behaviour immediatly and now i completly missed it.

Quote:
Well you could get away with that ofcourse (not using icaros) but the problem is/was in the nightlies also Which would mean you are gonna run into this sooner or later...

But as i told, i had to check nightlies first (did not come to it until now).

The good news is: i can double click again running commands from within dopus

Also good news is: i can run multiview again within dopus using a button .

One drawback is still left: the multiview pubscreen option does not work. multiview is always opened on the workbench screen. But perhaps this can be cirumvented by using workbench command instead of amigados and checking the option to put opened window upfront (didn't test it myself).

All tried and tested on clean installed abiv0 nightly from feb 23th.

Thank u, whoever you are, for fixing this (doing so intentional or not)

just fwiw

I also use DOpus for almost everything. But I don't use Icaros so I can not comment on that. Seams like a Icaros problem.

Maybe because I use Dopus almost for everything. Others maybe do things from Wanderer.

Tried and reproduced the error four times now (using the same install and upgrade path) with patch 03.

Icaros 1.3.3 with no patch and with patch 01 all works ok. It goes haywire for me with patch 03 when changing the pubscreen option.

Also double clicking a (runable) file in dopus stopped executing (also this worked properly before patch 03)...

Using icaros 1.3.3 full -> Patch 01 -> Patch 03

Next thing is to figure out what changed (and tbh in patch 03 a lot of things changed that is/can be related/resposible)

regards,

P.S. pretty strange we 3 people seem to be the only ones in whole aros-land that suffer from this reproducable error

Quote:

No need to forgive anything. English is also not native for me. And i tend to go into steno-modus when reporting so that does not make it easier

Quote:

Well guess what ?
I was preparing to provide proof but i thought to myself: why not try to run dopus in it's own screen and try the PUBSCREEN option also -> to make it more evident.

The result was it did not work. So i set dopus back to run on the workbench again and removed the PUBSCREEN option from the multiview button.

Guess what ?

It stopped working alltoghether. So no multiview anymore :(

So that leads me to believe something changed within dopus settings that cause this behaviour. So i guess dopus configuration tool makes use of a function within icaros that was updated/changed with the patches.
Which function that migth be is beyond me atm.

Now come's the even more boring part. In order to check this i have to do all installation sequence again and check with and without PUBSCREEN option in order to verify where it goes wrong (e.g. which patch is responsible if at all).

so i guess this tells us multiple partitions is not the culprit here.

regards,

Please forgive me... sometimes I don't understand the meaning of some sentences. It's only due to my bad english. And I don't think you are cheating.