Oh please no more conspiracy theories I just meant hopefully "in time" for the next public update (whatever and whenever that will be) .. this bug is really old enough already.
AmigaOS 4 core developer www.os4welt.de - Die deutsche AmigaOS 4 Gemeinschaft
"In the beginning was CAOS.." -- Andy Finkel, 1988 (ViewPort article, Oct. 1993)
I didn't ask, but I'd guess that it was an accidental side effect of some other change and no one had noticed that a long title string didn't work any more. The actual change was some time ago.
Unfortunately, that's one of the effects of having a group of betatesters rather than a formal battery of tests. We have to hope that everything testable is tested by someone, somewhere, on some hardware and with some installation. It doesn't always happen.
I didn't ask, but I'd guess that it was an accidental side effect of some other change and no one had noticed that a long title string didn't work any more. The actual change was some time ago.
Thank you
Quote:
Unfortunately, that's one of the effects of having a group of betatesters rather than a formal battery of tests. We have to hope that everything testable is tested by someone, somewhere, on some hardware and with some installation. It doesn't always happen.
Well, thats what you have the community for. There will always be some nutties (ME!!!) trying stuff other than normal day's work
It's absolutely fabulous that we as a community can give feedback and actually be able to see changes happen, bugs squashed and features taken care of.
Thanks to you and all of the devs for being so responseful, it's just great to be part of it
Chris wrote: Hmm, I see the old pattern-matching bug is still present. I will continue to mention this until it finally gets fixed.
5.RAM Disk:> dir files ABAB ABBA 5.RAM Disk:> dir #(AB|BA) 5.RAM Disk:>
Hm... I remember investigating that ages ago and even started to work on it.. Or at least it was on my todo list. I'll recheck with Colin to get this finally fixed, hopefully in time.
Chris is doing it wrong!
dir #?(AB|BA)
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
No what Chris is trying to write is something that translate fro mthe english : any number of occurence of either AB either BA. This should match AB, BA, ABAB, BABA, ABBA, BAAB, etc. If you prefer a way to represent this regex (if you understand them) : (AB|BA)*
What you are asking with #?(AB|BA) is to match everything ending with either AB, either BA.
I've got a uA1c with 256MB RAM running OS4.1 for AmigaOne. 1280x720, 16-bits.
I can confirm there is a bug in the Compositing Engine on uA1c's, at least on mine .
Strange graphic problem - 'Noise' with Composition Engine enabled ---------------------------------------
If I enable the Composition Effects in the GUI Prefs, I sometimes get small pixel errors, it's hard to describe it, it's not trashed pixels. More like "noise". It can move to different parts of the screen. And then it's gone. It's just a few pixels each time.
Has anybody else noticed this problem? What the h*ll could it be? I've checked the cabling, and it's no problem.
If I switch CE off in the 'GUI' prefs, I don't get this problem.
Drag&Drop in Workbench doesn't work with Composition ENgine ---------------------------------------------------------
I can confirm this, D&D will NOT work with the Composition Engine, the D&D aborts very rapidly. If I switch off the Comp. Eng., D&D works perfectly.
ALSO, but I'm not 100% sure, the Mouse wheel will stop working in some applications.
No what Chris is trying to write is something that translate fro mthe english : any number of occurence of either AB either BA. This should match AB, BA, ABAB, BABA, ABBA, BAAB, etc. If you prefer a way to represent this regex (if you understand them) : (AB|BA)*
What you are asking with #?(AB|BA) is to match everything ending with either AB, either BA.
so Chris is tring to do:
dir #?(AB|BA)#?
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
No, that would match things like XABQ. I'm trying to do exactly what I typed and abalaban has described. Try it on AmigaOS prior to OS4 and you'll see it working as it should.
Drag&Drop in Workbench doesn't work with Composition ENgine ---------------------------------------------------------
I can confirm this, D&D will NOT work with the Composition Engine, the D&D aborts very rapidly. If I switch off the Comp. Eng., D&D works perfectly.
This has been discussed before (hmm, maybe not here, but at least over there). Something is locking (updating) the WB screen at regular intervals for too long each time, causing the D&D operation to time out and terminate. In my case it was DOpus 4, iconified to the little title bar with the clock, showing seconds. When I changed DOpus to iconify to a "real" appicon instead and found another way to have an onscreen time display (LimpidClock), the problem was gone.
No, that would match things like XABQ. I'm trying to do exactly what I typed and abalaban has described. Try it on AmigaOS prior to OS4 and you'll see it working as it should.
Also, LiveForIt, try reading up on the weird and wonderful world of AmigaOS pattern matching. In daily use, many tend to just use the "#?" combination as if it was exactly equivalent to the "*" on other platforms and just a more long-winded way of writing it. This is only a small part of the story.
The "#" means something like "zero or more occurrences of the following element", and the "?" means "exactly one arbitrary character". Therefore, the often used combination, "#?", means "zero or more occurrences of exactly one arbitrary character", or more simply put, "nothing or anything" -- which also just happens to be what the "*" means in other OSes.
Back to "#(AB|BA)": This means "zero or more occurrences of the element (AB|BA)". This is one element because of the parenthesis, and the meaning of the element of course is either "AB" or "BA". So the whole pattern should match any number (zero or more) of consecutive character pairs, where each of them is either "AB" or "BA".
>This has been discussed before (hmm, maybe not here, but >at least over there). Something is locking (updating) the >WB screen at regular intervals for too long each time, >causing the D&D operation to time out and terminate. In my >case it was DOpus 4, iconified to the little title bar >with the clock, showing seconds. When I changed DOpus to >iconify to a "real" appicon instead and found another way >to have an onscreen time display (LimpidClock), the >problem was gone.
Niels,
Yes, I've read this discussion, also.
But, in this case, I've booted from a clean installation of WB4.1. Running no special programs at all, I removed all programs in WBStartup folder.
I still get the above mentioned behaviour when I try a simple copy operation by D&D'ing a file from RAM: to my SYS: partition.
This is why I'm lead to believe it's the Composition effects that's the culprit, because as soon as I switch them off (Comp. effects), D&D will start working perfect.
; This line triggers a DSI error!!!! copy >nil: envarc:sys/#?.prefs env:sys/ all
Did you remove Kickstart/env-handler.kmod from your Kicklayout (if yes: why?), or why do you want to do something manually env-handler does automatically, and only when required?
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
Donate
