Hi All,

This issue has been fixed in PowerBuilder 2019 R2 GA (Build 2323).

Please download this version or the latest PB 2019 R3 2670 and verify if it fixes your issue.

You can get the installer from our downloads portal at https://account.appeon.com/download/2019

You can refer to the bug fix list document (Bug ID: 323)

Https://docs.appeon.com/pb2019r2/release_bulletin_for_pb/bug_fixes.html

If the issue still exists in the new version, please report your issue via our support ticketing system to ensure it is being properly received and tracked by our tech support: https://www.appeon.com/standardsupport/newbug

Regards,

FWIW, I've commented on various bugs where Appeon tells customers that things have been resolved that it's NOT. But ... why listen to me.

:)

Hi , 

We have same problems with RDP. I tried in W10 and when I open the application directly, the scroll option works correct. If i connect to RDP not works correct . The application move one page on DW rows. 

Can be problem how read Appeon applications Computer\HKEY_CURRENT_USER\Control Panel\Desktop\WheelScrollLines from windows register when is executed in RDP session.  I see in my windows register the WheelScrollLines is 3 and works correct when i execute the Appeon program directly on the PC. 

Regards, 

Andrei 

I've updated (again) the code that I previously pasted here. It wasn't working at all, my apologies.

I've updated my solution with some setredraw() to prevent the scroll to become 'sluggish'.

I have NOT updated the sample application that I also posted here previously.

New code:

CONSTANT uint WM_MOUSEWHEEL = 522

CHOOSE CASE message.number
	CASE WM_MOUSEWHEEL
		// v1 and v2, mjl, 13/04/20: Since win8 and w10 totally ignore the mouse settings when working remotely, I've re-introduced the code to scroll:
		// First check the user isn't "zooming" by using CTRL+mouseWheel:
		IF KeyDown( keyControl!) then
			RETURN 0
		END IF
		CONSTANT uint SPI_GETWHEELSCROLLLINES = 104
		CONSTANT Long WM_VSCROLL = 277
		CONSTANT Long SB_LINEDOWN = 1
		CONSTANT Long SB_LINEUP = 0
		
		int li_WheelMouseLine, li_index
		int li_lines

		// Function boolean SystemParametersInfoW(uint wActon, uint wParam, REF int pvParam, uint fUpdateProfile) Library "USER32.DLL"
		SystemParametersInfoW(SPI_GETWHEELSCROLLLINES, 0, ref li_WheelMouseLine, 0)
		li_lines = IntHigh(wParam) / 120
		this.SetRedraw(false)
		IF li_lines > 0 THEN
			FOR li_index = 1 TO li_WheelMouseLine
				Send(Handle(THIS), WM_VSCROLL, SB_LINEUP,0)
			NEXT
		ELSE
			FOR li_index = 1 TO li_WheelMouseLine
				Send(Handle(THIS), WM_VSCROLL, SB_LINEDOWN,0)
			NEXT
		END IF
		this.SetRedraw(true)
		message.processed = true // don't process the event anymore, since we've already dealt with it.
		RETURN 1 // even when people claim it should be 0 !!!
END CHOOSE

RETURN 0

Hi Andres;

  Yes, this is a "legacy" issue dating back to the Sybase versions of PB. The mouse scrolling issue has certainly been well reported with RDP and Citrix software even in the PB 12.6 days. Of course, Appeon PB is based on the PB 12.6 codeline - which is what SAP turned over to Appeon in 2016 and what PB2017 and higher versions are based on. 

  I also suspect that other remote software (ie: like Andres reports) will also have this issue. If you reported this issue before through a support ticket, please post a response asking engineering for an update.

Regards .. Chris

Here's a little sample application, made with  PB2019 R2: see attached

(Edited: I've changed the type of WM_MOUSEWHEEL to uInt as Message.Number is an unsigned int.)

Hi Andreas,

I've tested your case (not using RDP, but a differenct remote connection "Splashtop") and indeed, W10 seems to ignore the settings for the line-scroll. It scrolls a page, always when on remote.

Honestly I think this is a Windows 10 problem and not an Appeon problem.

Anyway, long story short, here's some code to solve your problem.

You have to declare this external function:

Function boolean SystemParametersInfoW(uint wActon, uint wParam, REF int pvParam, uint fUpdateProfile) Library "USER32.DLL"

And  then paste this code in the datawindow's "other" event.

CONSTANT uint WM_MOUSEWHEEL = 522

CHOOSE CASE message.number
	CASE WM_MOUSEWHEEL
		// v1 and v2, mjl, 13/04/20: Since win8 and w10 totally ignore the mouse settings when working remotely, I've re-introduced the code to scroll:
		// First check the user isn't "zooming" by using CTRL+mouseWheel:
		IF KeyDown( keyControl!) then
			RETURN 0
		END IF
		CONSTANT uint SPI_GETWHEELSCROLLLINES = 104
		CONSTANT Long WM_VSCROLL = 277
		CONSTANT Long SB_LINEDOWN = 1
		CONSTANT Long SB_LINEUP = 0
		
		int li_WheelMouseLine, li_index
		int li_lines

		// Function boolean SystemParametersInfoW(uint wActon, uint wParam, REF int pvParam, uint fUpdateProfile) Library "USER32.DLL"
		SystemParametersInfoW(SPI_GETWHEELSCROLLLINES, 0, ref li_WheelMouseLine, 0)
		li_lines = IntHigh(wParam) / 120
		this.SetRedraw(false)
		IF li_lines > 0 THEN
			FOR li_index = 1 TO li_WheelMouseLine
				Send(Handle(THIS), WM_VSCROLL, SB_LINEUP,0)
			NEXT
		ELSE
			FOR li_index = 1 TO li_WheelMouseLine
				Send(Handle(THIS), WM_VSCROLL, SB_LINEDOWN,0)
			NEXT
		END IF
		message.processed = true // don't process the event anymore, since we've already dealt with it.
		this.SetRedraw(true)
		RETURN 1 // even when people claim it should be 0 !!!
END CHOOSE

RETURN 0

Hello Appeon Team,

Can we please have some updates on this issue.

Thanks,