Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved Mouse Wheel Scroll not Working

  1. Issue
0
Votes
Undo
  1. Luiz Marques
    Luiz Marques
  2. PowerBuilder
  3. Tuesday, 5 January 2021 15:24 PM UTC

Good afternoon, 

        I have done a migration recently for a client from the version 7 to the version 2019 R2. Everything was resolved except one issue with one screen that the client is complaining that the mouse wheel scroll is not working. On our environment 3 people in the company tried to replicate without success, the mouse wheel scroll is working fine, in my case I was able to replicate, in my machine is not working and in the client as well. I'm using pb 2019 R2 the latest build, Windows 10 and a logitech mouse. Someone in the forum faced this issue? If yes, there is some work around to fix that? Please, let me know as is the only pending issue in the project and I'm stuck with this issue... 

oleobject.Selection.typetext(sVal) function is get...
PB Classic - NON Active Directory Sync
Responses (3)
John Fauss
John Fauss Accepted Answer Pending Moderation
  1. Tuesday, 5 January 2021 15:53 PM UTC
  2. PowerBuilder
  3. # 1

Greetings, Luiz - 

Can you please supply some additional information? In regards to the particular machines where the mouse wheel is NOT working:

Is the user connected locally (phyically) to the machine? Accessing through Remote Desktop? Citrix? Other?

Is the PB 2019 app locally installed on each machine?

What is the mouse wheel input supposed to be affecting? A DataWindow? Rich text edit? Multi-line edit? Entire window? Zoom in/out? Does the mouse wheel work anywhere within the app, or just not in certain places within the app?

Does mouse wheel work in other apps (Word, Outlook, Windows Explorer, web browser) on these machines otherwise?

When you say you're migrating "from version 7" are you referring to PB v7 or Windows 7?

Do all machines have the same set of PB 2019 run-time DLL's installed?

Regards, John

Comment
Luiz Marques
  1. Luiz Marques
  2. Wednesday, 6 January 2021 16:31 PM UTC
0

Votes

Yes, my specific machine and in the client machines (I don't know if all the machines in the client).







Is the user connected locally (phyically) to the machine - Locally (like me during my tests where not working for me as well)



Is the PB 2019 app locally installed on each machine? On my machine the PB IDE is installed locally and not working, in the client they're using the PB runtime installation.







What is the mouse wheel input supposed to be affecting? A DataWindow? Rich text edit? Multi-line edit? Entire window? Zoom in/out? Does the mouse wheel work anywhere within the app, or just not in certain places within the app? It's an ole object => ctSchedule.ocx. Work for some people, do not work for others, etc.







Does mouse wheel work in other apps (Word, Outlook, Windows Explorer, web browser) on these machines otherwise? Yes, do not work on this specific screen, even on others screens the mouse scroll works, this is a specific screen that uses this ole db reponsible for schedule transportation, allocate a driver to specific destination, etc. It's clear for me that is something related with the OLE Object, but why works for some people and do not work for others? I mean, the SO is the same (windows 10), The issue is happening in the client without the IDE installed, they're running from the executable. (The ocx is installed in there as the most of the screens use this ocx, is the main object in the application).







When you say you're migrating "from version 7" are you referring to PB v7 or Windows 7? PowerBuilder 7 to 2019 R2



Do all machines have the same set of PB 2019 run-time DLL's installed? Yes
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 5 January 2021 16:43 PM UTC
  2. PowerBuilder
  3. # 2

Hi Luiz;

  Food for thought ....  It could be that that one screen has been mapped to low level events and somehow, this is now interfering with the mouse wheel. Check your troublesome Window and its controls for mapped user events. Especially keyboard & mouse activity.

  The other issue that can affect this behaviour is when the PB App(s) are run via Citrix or through RDP. These environments are known for hindering the Mouse Wheel behaviour.

Regards ... Chris

Comment
There are no comments made yet.
John Fauss
John Fauss Accepted Answer Pending Moderation
  1. Wednesday, 6 January 2021 15:35 PM UTC
  2. PowerBuilder
  3. # 3

Thanks for responding to my plethora of questions. Luiz.

I don't have a definitive answer for you, But, since the mouse wheel functionality appears to be working in other apps and in other areas of the PB application, this makes me think the issue may be the OCX. Have you tried to un-register and re-register it? Have you verified the same version of the OCX is being used in working and not-working PC's?

Here's a link that may help if you are not familiar with the steps:

https://silicophilic.com/register-and-unregister-dll-and-ocx-files/

You may also wish to contact the vendor/supplier of the OCX to see if this is a known issue. If so, they may have a fix.

Please let us know if this helps?

Comment
Luiz Marques
  1. Luiz Marques
  2. Wednesday, 6 January 2021 16:30 PM UTC
Thanks for your help. Yes, I've tried to unregister and register the ocx again and no success. The ocx version is the same for the working and not working PC's...... I think maybe is something related with the PB version as the client environment is the same and the version 7 executable works as expected. Maybe to runtime file of the pb 2019 R2 is not correct, missing sme specific code, I don't know... PB 2019 R2 dealing with the OCX object, I don't know, there is some difference as the version 7 works normally.
  1. Helpful
John Fauss
  1. John Fauss
  2. Wednesday, 6 January 2021 16:59 PM UTC
OK. It was worth a try. Keep in mind that PB changed internally from ANSI to Unicode in v10. That was a significant change. I'm not saying it's the cause of this problem, just pointing out that it MIGHT be a factor. is there a more recent version of the OCX that is available to try?
  1. Helpful
John Fauss
  1. John Fauss
  2. Wednesday, 6 January 2021 17:07 PM UTC
ctSchedule.ocx v12 (released March 24, 2015) added support for Unicode. v15.0 is the latest version (March 2019).
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.