I think I found a solution for anyone who wants to be able to scroll with the mouse wheel, while working from home:
Since I don't have the problem, as I'm using no RDP, I logged on to a test pc at my job and from that pc, connected to my own pc at the job, using RDP: efectively, no scrolling works in the script editor window.
After installing it, I recommend to say "yes" to show the readme which has all to information (and of course I did not read).
It's very simple: Once installed and having said 'yes' to run it, you'll see a small icon in the system tray. Right click on it and go to settings. Then on the third tab page ("applications") click on the "add" button and browse to whichever version of pb.exe you are using.
Sometimes the "Find" window seems to be invisible for me (it still works, though - [ctrl]-[f], type, [enter], and it does what it's supposed to, you just can't see the window). Closing PB and reopening it usually solves the problem, though.
To quote the immortal words of standard nerd Roy Trenneman: "Hello, IT, have you tried turning it off and on again?"
Just started at a new employer, working from home, using Citrix into dev machine in another state, which has PB2021. Mouse wheel scrolling appears to work for everything EXCEPT Script painters in PB. System Tree, Output window, event and function lists, even the dropdown lists for window events in the script painter work with the wheel, but the script itself remains motionless when trying to scroll with the mouse wheel. Very frustrating, and sad to see this was reported years ago and still not fixed.
Yes, I've been having the same issue in the script window using RDP since PB 2017. 3rd party apps aren't allowed to be downloaded and installed on my VM, so the workaround fix suggested above won't do. Appeon should fix this.
I have discovered that the problem is ONLY in powerbulder. I use Powerbuilder 2019 R2.
It is NOT an issue of Windows !!
It's simply: i have a developer coputer with windows 10 and Powerbuilder IDE 2019 R2. When I start my application from IDE and I start a wndow with an Rich Text Edit control... the mouse works very well.
If I deploy the application setting "64 bits pcode" to my connected secondary computer with 64 bits powerbuilder runtime installed.... the application shows the RTE control aligned on left of window, without status bar... and other differences respect the version which I see in the IDE environment and the mouse wheel DOES NOT work.
If I deploy the application, setting "32 bits pcode" to my Win-10 secondary computer with 32 bits powerbuilder runtime installed.... the application shows the RTE control well fitted in the middle of window, with everything exactly the same like I see in the IDE environment and the mouse wheel WORKS PERFECTY.
The type of RTE control that I setted is : "Built-in TX Text Control", always.
I am very much upset because mouse wheel and because the differences in the behaviour of the RTE control (different position, different bars, no status bar,...)
So, to solve all problems I and everyone should deploy 32 bits Pcode application.
Someone can explain me what my client loose, respect a 64-bits Pcode application or if someone has found a method to have the same visual control in 32-bits and in 64-bits application (attached the screenshots of both situations) ? Thank you very much
Hi Fabrizio ... FYI: the 64bit RTE or RT DW in PB2019R2 is based on the *Microsoft* RTE control. Thus, it has a much different look & feel than the TX/TE control in a 32bit App (as run from the IDE as well). As you can see from your screen captures that you posted.
In PB2019R3, Appeon changed the RTE options by adding a 64bit TX control. Thus, if you choose the TX option in R3, both the 32bit and 64bit RTE's behaviour should be the same. HTH
This is still a PowerBuilder IDE issue with PB 2017, PB 2019 R2, R3 release and IMHO its not a windows issue. Windows behaves correctly in every other application I use, MS Edge, OFFICE products, Outlook, Firefox, Heck even notepad and word pad works correctly... All while in my RDP session using either MS RDP or CISCO tools.
The problem does not happen if you are locally running PowerBuilder, but in this "cloud" and VM world we now live and work in, who has local content on their machines is rare I would say. Clients want their developers and their source code as close to their machines as possible off local laptops and local PCs for source control and security reasons mostly.
Software/Hardware: Windows 10 Pro Version 2004 OS Build: 19041.804 running a Logitech Mouse 810-00633 G300S Again really not a issue of the OS version or Hardware, I have many versions of windows the problem has occurred on other platforms in the VM environments. It happened in Windows 7, Windows 2012 Server (Yes don't lecture me about running PB IDE on a server machine, that's ancient history, but the problem also existed under Win2008/2012 server)
Its a huge productivity hit, Visual Studios doesn't have this debilitating behavior why should anyone tolerate this is beyond me. I work exclusively in VM's nowadays, Hyper-V or VMWare VM's either using RDP or Cisco tools to connect, the problem is widespread all over the place. Some engineer assistance to fix this problem properly would make a lot of happy developers.
Come on Appeon, put in the effort to resolve this once and for all please.
Hi, IMHO it is definately a PB Problem so please don't put us off from above with comments that Windows (TS) Server is not supported...
For my sake, i'm using PB 2019 on a Windows 10 1909 Build 18363.752 Build 2170 with a Logitech MX Master in my Office with Powerbuilder. All scrolling there is fine.
Due to Covid I'm now in my Home office on Windows 10 1909 Build 18363.752 using RDP to connect to the Office Machine. At home I have a Logitech MX518 unsing standard windows drivers. Also tried a MS-Mouse.
Exactly the same problem thread starter mentioned can be confirmed here: No mouse scrolling in scripts via RDP in Powerscipt.
Mouse scroll works fine in PB IDE Library List. in Visual Studio Code, Visual Studio 2019, all office programs, all browsers (Firefox, Chrome, Edge).
For my case solely but pretty annoying is that the PB Script is affected.
Also working from home and seem to remember that this mouse scrolling using the wheel didn't work using RDP or maybe that lots of times it didn't work and had to close powerbuilder and open up again (or was that the "search" using the keyboard?)
Anyway, not a solution maybe for everyone, but I've tested my remote connection using "Splashtop" and the scrolling does work. Splashtop is pretty good and very cheap.
I've also tested using "ConnectWise" and the scrolling also works. Connectwise is also very good and possibly free.
It is clear that there is a problem with the mouse wheel when you are editing the code and it is done from a remote desktop, it doesn't matter to reinstall PB, it doesn't matter to reinstall the mouse drivers, it is a problem that Appeon must face, it would be exceptional if a patch came out, we are programmers and it is very very annoying to edit code as to create it, a lot of time is lost.
Remember, we are working from home and it is not because we want to. Appeon should at least make it easier for us to work on a tool with such a high price tag.
Yep this COVID19 crap has everyone at home and relying on RDP and pulling their hair out on these script windows. A coworker and I are both having this issue. We both RDP into our desktop computers which are running Win10 1909 and both of us have the same Logitech mouse (server side, not at the house). When I find some time I wanted to try uninstalling SetPoint (on the server side) to see if that has any impact. SetPoint also has the ability to disable smooth scrolling on specific applications. I was going to try that too.
I would love to know if everyone having problems with RDP is also using a Logitech mouse. I would also like to know if there is anyone that is not having this problem and if so, what mouse are they using.
In effect, Terminal Services with PB are not supported. But this seems to be a know windows issue. By doing a quick Google search it was not difficult to find many similar cases happening here and there.
Hmmm .. that is very weird. I have been on W10 for 4 years and using PB 2017 for about a year now (from starting with 2017 beta). I have had no mouse scrolling issues in the PowerScript Painter (or even my PB Apps') from my perspective on any of my 3 development machines. My PC's are all now on the W10 Fall Creator Edition and running PB 2017 R2.
I wonder if this is a mouse driver issue on your PC?
FWIW: I only use Logitech mice and my PC's are all AMD based processors.