Proteus Middle Button Stays Pressed When Panning

[hyprfrcx]

In the Proteus 8.6 user interface, when pressing the middle button for panning the schematic sheet, the function got frozen, as if the button stays pressed...

A little annoyance, but it would be nice to have the natural behaviour of every other software around.

Can that behaviour be changed?

Thanks in advance.

 

[andre_luis]

Unless knowing what functions are being instantiated in the code upon the pressing of the button, it is difficult to guess whether the frozen berhaviour is just a colateral effect of the user interaction instead the cause itself. Are you using interrupt to detect pin change? What microcontroller? what compiler?

 

[hyprfrcx]

Hello,

I am talking about the Proteus 8.6 Design Suite, LabCenter Electronics software.

 

[andre_luis]

Ok, I got it; I thought you were referring to the interaction with a tactile button within the schematic. To be honest, I've never seen such a behavior (indeed, never did it). Have you tried assigning higher execution priority in Windows to Proteus?

 

[hyprfrcx]

No, hehe, i am not talking about anything sophisticated, just navigating inside a schematic.

I already configured several Keyboard Mappings, but i am asking if the panning through the middle button works that way, or is just my case for some weird reason. I could remember this behavior is also in previous versions of Proteus, but not fully sure.

By changing the priority setting of the Windows Process in the Task Manager put into High instead of Normal didn't have any effect.

Proteus:
- Click and release middle button, for enter panning mode,
- Do panning through the sheet, on the viewable screen,
- Click and release again, for exit panning mode.

Other software:
- Click and hold for enter panning mode,
- Do panning,
- Release for exit panning mode.

 

[andre_luis]

Proteus:
- Click and release middle button, for enter panning mode,
- Do panning through the sheet, on the viewable screen,
- Click and release again, for exit panning mode.

Here behaves exactly as you said, and it is fine for me, so it really does seem that the Tool is capturing the Mouse events to manage it by its own manner distinctly from the operating system (or, oppositely are the other programs doing this? :???