I'm running Openedge client networking 11.1 (also tried with webclient) on a windows 8.1 tablet and I'm having issues getting the Windows wait cursor to display.
The code works fine on my own machine (11.5 Progress Developer Studio / Windows 7). Has anyone encountered this before or have any ideas? Thanks in advance! I have tried both the general cursor and a custom cursor. Input is blocked but the user is not getting the visual feedback and spams the touch-screen.
The code is as simple as:
SESSION:SET-WAIT-STATE ("cursor.cur").
DO WHILE ETIME < 10000:
ASSIGN fiResult = STRING(ETIME) + " - " + SESSION:GET-WAIT-STATE ().
DISPLAY fiResult.
END.
MESSAGE "Turning off wait state"
VIEW-AS ALERT-BOX.
SESSION:SET-WAIT-STATE ("").
Any ideas would be appreciated.
It's a windows 8 issue apparently. As I mentioned in my first post, this is running on a Windows 8.1 tablet. Microsoft, in their wisdom decided to change OS behaviour in Windows 8 to not load any kind of pointers/cursors when there is no mouse/keyboard attached. I took the wireless keyboard USB dongle from my laptop and connected it to the tablet and hey presto, the WAIT cursor gets re-enabled and the code works fine. Thanks for your comment though!
I'll need to create some home made wait logic and flash up a wait frame to block input I think.
Could it be that you should use:
SESSION:SET-WAIT-STATE("GENERAL").
instead?
-------- Original Message --------
> From: "beefhealy"
> Sent: Monday, September 21, 2015 12:50 PM
> To: TU.OE.General@community.progress.com
> Subject: [Technical Users - OE General] SESSION:SET-WAIT-STATE has no
effect
>
> Update from Progress Community [https://community.progress.com/]
>
> beefhealy [https://community.progress.com/members/beefhealy]
>
> I'm running Openedge client networking 11.1 (also tried with webclient)
on a windows 8.1 tablet and I'm having issues getting the Windows wait
cursor to display.
>
> The code works fine on my own machine (11.5 Progress Developer Studio /
Windows 7). Has anyone encountered this before or have any ideas? Thanks in
advance! I have tried both the general cursor and a custom cursor. Input is
blocked but the user is not getting the visual feedback and spams the
touch-screen.
>
> The code is as simple as:
>
> SESSION:SET-WAIT-STATE ("cursor.cur").
>
>
> DO WHILE ETIME
>
> ASSIGN fiResult = STRING(ETIME) + " - " + SESSION:GET-WAIT-STATE ().
>
>
> DISPLAY fiResult.
>
> END.
>
>
> MESSAGE "Turning off wait state"
>
> VIEW-AS ALERT-BOX.
>
> SESSION:SET-WAIT-STATE ("").
>
> Any ideas would be appreciated.
>
> View online
[https://community.progress.com/community_groups/openedge_general/f/26/t/202
98]
>
> You received this notification because you subscribed to the forum. To
stop receiving updates from only this thread, go here
[https://community.progress.com/community_groups/openedge_general/f/26/t/202
98/mute].
>
> Flag
[https://community.progress.com/community_groups/openedge_general/f/26/t/202
98?AbuseContentId=780e778e-08ff-49b5-b379-7c1316c81bfa&AbuseContentTypeId=46
448885-d0e6-4133-bbfb-f0cd7b0fd6f7&AbuseFlag=true] this post as
spam/abuse.
Hi Mark,
I used that code initially and it has the same problem. I used the custom cursor to rule out an issue with the default cursor. Thanks.
Hi,
Another good idea would be to add a PROCESS EVENTS just after you set the
wait state - that will give the client time to change its UI before going
into the WHILE loop.
-------- Original Message --------
> From: "beefhealy"
> Sent: Monday, September 21, 2015 1:43 PM
> To: TU.OE.General@community.progress.com
> Subject: RE: [Technical Users - OE General] re: [Technical Users - OE
General] SESSION:SET-WAIT-STATE has no effect
>
> Update from Progress Community [https://community.progress.com/]
>
> beefhealy [https://community.progress.com/members/beefhealy]
>
> Hi Mark,
>
> I used that code initially and it has the same problem. I used the custom
cursor to rule out an issue with the default cursor. Thanks.
>
> View online
[https://community.progress.com/community_groups/openedge_general/f/26/p/203
01/71901#71901]
>
> You received this notification because you subscribed to the forum. To
unsubscribe from only this thread, go here
[https://community.progress.com/community_groups/openedge_general/f/26/t/203
01/mute].
>
> Flag
[https://community.progress.com/community_groups/openedge_general/f/26/p/203
01/71901?AbuseContentId=914d2d8d-aa55-46e3-84a5-4634df8a1426&AbuseContentTyp
eId=f586769b-0822-468a-b7f3-a94d480ed9b0&AbuseFlag=true] this post as
spam/abuse.
It's a windows 8 issue apparently. As I mentioned in my first post, this is running on a Windows 8.1 tablet. Microsoft, in their wisdom decided to change OS behaviour in Windows 8 to not load any kind of pointers/cursors when there is no mouse/keyboard attached. I took the wireless keyboard USB dongle from my laptop and connected it to the tablet and hey presto, the WAIT cursor gets re-enabled and the code works fine. Thanks for your comment though!
I'll need to create some home made wait logic and flash up a wait frame to block input I think.