Difference: 0LASubrClientCheckForGui (2 vs. 3)

Revision 32015-04-27 - JeanNeron

Line: 1 to 1

META TOPICPARENT	name="APPXRuntimeSubroutineAPI"

.CLIENT CHECK FOR GUI

Line: 7 to 7

.CLIENT CHECK FOR GUI

Usage:

      PASS         <gui>                      FIELD            SHARE? Y

Added:

>
>

PASS <type> FIELD SHARE? Y

GOSUB --- .CLIENT CHECK FOR GUI

- Check for errors IF --- .CLIENT CHECK FOR GUI NE

Line: 14 to 15

Description:

Changed:

<
<

This subroutine returns a flag to indicate if the user is running the Desktop Client. The <gui> parameter is required, if it is missing the subroutine will CANCEL.

>
>

This subroutine returns a flag to indicate if the user is running a GUI Client or not. The <gui> parameter is required, if it is missing the subroutine will CANCEL.

<gui> will return either a Y or N, depending on whether the user is running the Appx Desktop Client (Required). This must be PASSed with Share "Y" to return a value.

Added:

>
>

<type> will return the type of GUI client (5.4.2 & higher only). It will return "A" for Appx Desktop Client (aka Java Client) and "H" for the HTML client (Optional). This must be PASSed with Share "Y" to return a value.

This does not indicate if the client is in GUI or Character mode, only that they are running the desktop client.

Comments:

View topic | History: r5 < r4 < r3 < r2 | More topic actions...