OS 3.2.x and (classic) Directory Opus 4.16 Mouse Wheel problems

tomcat666 · 03 March 2023, 16:45

Hello

When using a mouse wheel - any system (micromys from individual, hid2ami or plain old WinUAE without any drivers) on OS 3.2.x and using the classic Directory Opus 4.16 (or any other version really) you get very erratic behavour - sometimes mouse wheel events get lost, sometimes it will just freeze up for a while or crash completely.
Note that Directory Opus on 3.1 works perfectly fine with all Mouse Wheel drivers, so it is something in 3.2.x system that gives this behaviour.
It is also the same if one starts the freewheel program (which shouldnt be needed on 3.2 ... ).

Best regards,
Tomaz

shelter · 05 March 2023, 11:58

Yeah I noticed this as well. It's very annoying.

But what you can do instead is right clicking on top and bottom of the panes to scroll.

tomcat666 · 05 March 2023, 15:35

Yes, you can scroll with other means, but this is still one of the most used applications on the Amiga and will probably ever be. It is a shame such a but slipped through 3.2.x OS releases.

Michael · 06 March 2023, 05:45

Interesting, could it be due to configuration issues of the drivers ?

In WinUAE it works just fine without any additional drivers

tomcat666 · 06 March 2023, 06:47

Quote:

Originally Posted by Michael

Interesting, could it be due to configuration issues of the drivers ?

In WinUAE it works just fine without any additional drivers

It actually doesn't work fine ... It has the same problems as on real Amiga with ay driver. Just try a big directory and scroll up and down with the mouse wheel a few times and then try clicking on a directory and do this a few times...

shelter · 06 March 2023, 08:11

The question is tho', is the AmigaOS 3.2.x implementation buggy or is it DOpus being buggy.

tomcat666 · 06 March 2023, 10:13

Quote:

Originally Posted by shelter

The question is tho', is the AmigaOS 3.2.x implementation buggy or is it DOpus being buggy.

Hard to say, it was working perfectly fine on OS3.1 and below all the time, no such problems at all. It could be that an actual fix in OS 3.2.x broke this, but unfortunetly DOpus is not being developed anymore so a fix there is unlikely, it is possibly the most used application on Amiga (by those that are not just playing games) so it is quite important.

Michael · 08 March 2023, 17:56

Ok, confirmed, there is something going not entirely well and the event cue gets stacked up, and untill it clears you can't do anything else.

tomcat666 · 05 March 2024, 07:10

Well, for anyone that wants to use mouse wheel under OS 3.2.x and use Directory Opus 4.x there is a solution - use Hid2Ami adapter on real amiga, its wheel driver works 100% fine and perfectly with this combination. No problems whatsoever.

https://github.com/EmberHeavyIndustries/HID2AMI

StevenJGore · 05 March 2024, 07:40

Is the behaviour random, or can a certain sequence be easily reproduced? I've not noticed any weirdness with my USB mouse (using Anaiis USB stack and Subway USB adapter) on my A1200.

tomcat666 · 05 March 2024, 08:32

It is Dir Opus 4.x (for example 4.16) and OS 3.2.x related only.

Just go into a bigger dir and scroll up and down a while with the wheel, suddenly you can't even click on any directory entry anymore, nothing works for a while, then all of the sudden old clicks happen and things get back to normal. It is VERY easy to reproduce, happens almost every time here in winuae.

CCRider · 05 March 2024, 14:57

Can confirm this issue on my OS 3.2.2/DOpus 4.17pre system, using one of those new Tank Mouse with scrolling wheel sensor.

kiFla · 27 March 2024, 14:43

Also can confirm the same behavior with DOpus 4.17pre20, OS 3.2.2.1 with HID2Ami adapter. No, It doesn't work correctly with HID2Ami. Also freezing after scroll directory with a many files. (Dopus Magellan works great with scroll on same system.)

tomcat666 · 27 March 2024, 15:12

Quote:

Originally Posted by kiFla

Also can confirm the same behavior with DOpus 4.17pre20, OS 3.2.2.1 with HID2Ami adapter. No, It doesn't work correctly with HID2Ami. Also freezing after scroll directory with a many files. (Dopus Magellan works great with scroll on same system.)

Which is strange, since the same config here works fine.

kiFla · 27 March 2024, 15:15

Quote:

Originally Posted by tomcat666

Which is strange, since the same config here works fine.

Yes, very strange. Also no problems on OS 3.9 with same DOpus 4.17pre20.

wiz12 · 27 March 2024, 15:22

I think this is a problem with DOpus since this also occurs using a MouSTer adapter.

kiFla · 27 March 2024, 15:52

Quote:

Originally Posted by wiz12

I think this is a problem with DOpus since this also occurs using a MouSTer adapter.

There is no problem in OS 3.9 and 3.1.

Daedalus · 27 March 2024, 17:51

That doesn't mean it's not a problem with DOpus 4. It just means the problem doesn't show up under 3.9 or 3.1. There are enough variables at play here to rule out problems with everything, so it has to be a combination of factors. It's probably an interaction between DOpus 4 and the new mousewheel events introduced in OS 3.2. The good news is that DOpus 4 is open source, so someone can just go and fix it . . .

kiFla · 28 March 2024, 08:44

Yes, it make sense.

03 March 2023, 16:45	#1
tomcat666 Retro Freak Join Date: Nov 2001 Location: Slovenia Age: 51 Posts: 1,647	OS 3.2.x and (classic) Directory Opus 4.16 Mouse Wheel problems Hello When using a mouse wheel - any system (micromys from individual, hid2ami or plain old WinUAE without any drivers) on OS 3.2.x and using the classic Directory Opus 4.16 (or any other version really) you get very erratic behavour - sometimes mouse wheel events get lost, sometimes it will just freeze up for a while or crash completely. Note that Directory Opus on 3.1 works perfectly fine with all Mouse Wheel drivers, so it is something in 3.2.x system that gives this behaviour. It is also the same if one starts the freewheel program (which shouldnt be needed on 3.2 ... ). Best regards, Tomaz

28 March 2024, 08:44	#19
kiFla Registered User Join Date: Jul 2018 Location: Zagreb Posts: 9	Yes, it make sense. Last edited by kiFla; 28 March 2024 at 17:09.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
mouse wheel problems	xubidoo	support.Hardware	7	27 November 2019 16:57
Mouse wheel madness in Dopus (Classic Wb Lite v 24)	emuola	project.ClassicWB	9	26 September 2010 14:55
Help ! Problems with user menus and start menus in Directory Opus 5.8	beltrixx	support.Apps	0	27 May 2009 08:30
Directory Opus 5.5 on Classic WB adv?	Fingerlickin_B	project.ClassicWB	1	20 June 2007 10:11
Directory Opus	Djay	request.Apps	3	17 October 2002 01:39

05 March 2023, 11:58	#2
shelter Registered User Join Date: Nov 2022 Location: #Amigaland Posts: 156	Yeah I noticed this as well. It's very annoying. But what you can do instead is right clicking on top and bottom of the panes to scroll.

05 March 2023, 15:35	#3
tomcat666 Retro Freak Join Date: Nov 2001 Location: Slovenia Age: 51 Posts: 1,647	Yes, you can scroll with other means, but this is still one of the most used applications on the Amiga and will probably ever be. It is a shame such a but slipped through 3.2.x OS releases.

06 March 2023, 05:45	#4
Michael A1260T/PPC/BV/SCSI/NET Join Date: Jan 2013 Location: Moscow / Russia Posts: 840	Interesting, could it be due to configuration issues of the drivers ? In WinUAE it works just fine without any additional drivers

06 March 2023, 08:11	#6
shelter Registered User Join Date: Nov 2022 Location: #Amigaland Posts: 156	The question is tho', is the AmigaOS 3.2.x implementation buggy or is it DOpus being buggy.

08 March 2023, 17:56	#8
Michael A1260T/PPC/BV/SCSI/NET Join Date: Jan 2013 Location: Moscow / Russia Posts: 840	Ok, confirmed, there is something going not entirely well and the event cue gets stacked up, and untill it clears you can't do anything else.

05 March 2024, 07:10	#9
tomcat666 Retro Freak Join Date: Nov 2001 Location: Slovenia Age: 51 Posts: 1,647	Well, for anyone that wants to use mouse wheel under OS 3.2.x and use Directory Opus 4.x there is a solution - use Hid2Ami adapter on real amiga, its wheel driver works 100% fine and perfectly with this combination. No problems whatsoever. https://github.com/EmberHeavyIndustries/HID2AMI

05 March 2024, 07:40	#10
StevenJGore Amiga Fanatic Join Date: Feb 2004 Location: North Yorkshire, UK Age: 46 Posts: 727	Is the behaviour random, or can a certain sequence be easily reproduced? I've not noticed any weirdness with my USB mouse (using Anaiis USB stack and Subway USB adapter) on my A1200.

05 March 2024, 08:32	#11
tomcat666 Retro Freak Join Date: Nov 2001 Location: Slovenia Age: 51 Posts: 1,647	It is Dir Opus 4.x (for example 4.16) and OS 3.2.x related only. Just go into a bigger dir and scroll up and down a while with the wheel, suddenly you can't even click on any directory entry anymore, nothing works for a while, then all of the sudden old clicks happen and things get back to normal. It is VERY easy to reproduce, happens almost every time here in winuae.

05 March 2024, 14:57	#12
CCRider Registered User Join Date: Oct 2017 Location: São Leopoldo / Brazil Age: 46 Posts: 203	Can confirm this issue on my OS 3.2.2/DOpus 4.17pre system, using one of those new Tank Mouse with scrolling wheel sensor.

27 March 2024, 14:43	#13
kiFla Registered User Join Date: Jul 2018 Location: Zagreb Posts: 9	Also can confirm the same behavior with DOpus 4.17pre20, OS 3.2.2.1 with HID2Ami adapter. No, It doesn't work correctly with HID2Ami. Also freezing after scroll directory with a many files. (Dopus Magellan works great with scroll on same system.)

27 March 2024, 15:22	#16
wiz12 Registered User Join Date: Feb 2017 Location: Ireland Posts: 752	I think this is a problem with DOpus since this also occurs using a MouSTer adapter.

27 March 2024, 17:51	#18
Daedalus Registered User Join Date: Jun 2009 Location: Dublin, then Glasgow Posts: 6,343	That doesn't mean it's not a problem with DOpus 4. It just means the problem doesn't show up under 3.9 or 3.1. There are enough variables at play here to rule out problems with everything, so it has to be a combination of factors. It's probably an interaction between DOpus 4 and the new mousewheel events introduced in OS 3.2. The good news is that DOpus 4 is open source, so someone can just go and fix it . . .

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)