- Miguel Leeuwe
- PowerBuilder
- Monday, 24 January 2022 06:37 PM UTC
Not too long ago Appeon has updated the documentation / help to now state correctly that the Handle() function returns a Longptr value.
I see a lot of use of the function in the PFCs. We use Ulong for window handles (while the type of a handles and pointers are signed, as I've been told) and also Long variables.
Thinking of 64 bit compilation, could we run into problems and should we change all of the types to longptr where appropiate?
Another question I have, is whether we should be replacing "Get- and SetWindowLong(W)" calls to "Get- and SetWindowLongPtr", (excluding the "W", since compilationg would automatically take care of calling the correct function on 32 bit and 64): https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-setwindowlongptrw
I know this would be a hell of a job, it'll probably be a bit over my head to do this alone, and it would require a lot of testing.
Any ideas on how to tackle this or do you think we can safely run 64 bit executables without running into any problems?
regards,
MiguelL
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.