The Os 3.1.4 Thread

[kolla]

Like I wrote... a particular problem I have with original input.device, is that I cannot click on links in IBrowse using USB mouse, as if IBrowse doesn't get the "mouse-button release" event properly. I also recall problems with other programs (DOpus Magellan among them), but I don't recall exactly how the problems manifest themselves in the various programs. Because with input.device v50, these problems are not there.

Ok, I understand. Maybe. What I do not understand...

Why Chris did not do that is unclear to me.

So it looks like you don't really understand what input.device v50 "cludges" to make things work.

USB is a complex mess, with at least two protocols just for the mouse (bootmouse and hid) and ditto for keyboard, and lots of products in the market that break these protocols in various creative ways. Chris was very clear that using v50 input.device from MorphOS was only a half-way and quick solution for him, and that the entire input system for AmigaOS should have to be rewritten.

Thus, at this point, this looks like an implementation defect  at DOpus

DOpus, IBrowse, various other MUI software and whatever else that misbehaves with original input.device and Poseidon - you are now the one speculating ... educated speculation, but speculation nevertheless.

For DOpus it is easy enough to look for PeekQualifier in the code... I am not convinced that it is used in parts of the code relevant to where I experience trouble...

https://github.com/mheyer32/dopus5allamigas/search?q=PeekQualifier&unscoped_q=PeekQualifier

You also wrote...

All I can say is that I took precautions to address the problem, and I did my best to provide a solution.

yet...

The input device of 3.1.4 is the same as that of 3.1, and the only new thing it added was NSD. It does not provide any better solution than 3.1, but as of 3.1, there was already a correct way of doing it, namely create synthetic keyboard events yourself for keyboard repeat.

This is confusing. Unless the precaution was to not change anything, and to define "the problem" as non-existent.

Anyways - the best advice - as of now - for anyone using Poseidon with USB keyboard and/or mouse - is to load input.device v50 using LoadModule.

[kolla]

the ASL won't be opened because there is no space on the screen.

Imagine if it was possible to open a window larger than screen, and move it around with a qualifier + left mouse button pressed...

[kolla]

You are good at repeating how much you "have to" repeat the reason for me, yet no reason has been given, and certainly not repeated, other than "Windows does this" and some fictional arguments about third party commodities that may end up moving windows into a position where no gadgets can be reached... (something third party commodities can already do btw, regardless of window size) - no name of such commodity has been given, no demonstration of the so called problems have been given. Other windowing systems have no issues with this.  It is just another "because I say so".

[kolla]

As I wrote, the only thing you keep repeating, is that you are tired of repeating, you repeat that over and over when you have no better argument.

Why don't you instead come up with a solution to the problem described - what to do when a screen is too small for ASL requesters to show up? Obviously, only you can do it.

[kolla]

Thomas was awarding virtual points to any user guessing some of the new features that 3.2  brings. You guessed one: a working stderr.

If pointing out well known limitations and bugs in OS 3.1(.4(.1)) count as guessing new features for 3.2, then there are plenty of "virtual points" to be earned. Thomas has himself documented the issue with lacking support for stderr rather extensively in his Shell.guide for Shell v45 on aminet - this guide, with updates for v46 and future v47, should also have come as part of OS release.

http://aminet.net/package/util/boot/ShellUpdate

[kolla]

Part of the "issue" here is that in this case, *N does not expand to linefeed (but ***N does).


Edit: But after a little experimenting, this looks more like confusion over what %X is and how it works - lformat "%X1*n" works as expexted, with "%X*n" %X apparently just "swallows" the * and the n, while "%X *n" (space betweem X and *) does not. What's correct behaviour here is probably debatable, but I agree that it would be best to exit with error about bad template.

So, will C:Info and C:Date get LFORMAT too? And maybe C:Assign?

[kolla]

(Delete - double post)

[kolla]

Of course, "eval" cannot compute anything from that, so it prints an error.

Well, it doesn't print any error, and that's the real bug here.

[kolla]

Sorry, what? Eval prints an error.

OK, sure, if you say so - this "attitude of denial" is what I disliked when sending bug reports to you.

[kolla]

As my_pc_is_amiga wrote, on OS4 this makes more sense, eval gives an error.

[kolla]

e.g. with CycleToMenus.

with what?

http://aminet.net/search?query=CycleToMenus

"Found 0 matching package(s)"

What are you talking about?

[kolla]

Try the singular: CycleToMenu

Thanks!

If this functionality is so important that it affects OS development, then it should probably be incorporated.

[kolla]

It’s been on the list already, but don’t moan if it doesn’t make it into next release, ok?

I will only moan when it comes into the OS, but isn't possible to turn off.

Like the requesters of OS 3.1.4. They pop up with "Cancel" right under the mouse button... I never had any issue with requesters on Amiga, but now I find myself pressing "Cancel" by accident without even having had a chance to read what the requester was about. No way to turn _that_ damn "feature" off? I want the requesters to pop up like they used to - in the upper left corner, far away from where I am working, thank you very much!

[kolla]

No way to turn _that_ damn "feature" off? I want the requesters to pop up like they used to - in the upper left corner, far away from where I am working, thank you very much!

Have your tried the ASL prefs program to change position and then used the "Override application" option?

Turned out to not be related to OS 3.1.4, it was a third party commodity that did more than what documentation said it would.
So, my my apologies for moaning - on "naked" OS 3.1.4, requesters work as normal.

[kolla]

Is there a way to have this work?

Only way to have it work reliably, is to use a console replacement that features its own palette settings. One alternative is ViNCEd - http://aminet.net/package/util/shell/ViNCEd (note that this version is old, but newer versions are only included in OS 3.9, various boingbags and BestWB, with copyright Amiga Inc. - not as a single archive. Note also that these ViNCEd versions come with their own version of More which installs to S:, which is a script that work around an issue with original CBM More - this work-around is not needed with the More of OS 3.1.4 anymore, from what I understand... an updated VINCEd that get rid of confusing copyright notices and more "streamlined" installation for OS 3.1.4 owners would probably be a good idea)

[kolla]

What happens to "Fonts:" when you insert a disk labeled "Fonts"? Where does "Fonts:" take you?