Difference: APPXRuntimeSubroutineAPI (5 vs. 6)

Revision 62012-01-23 - JeanNeron

Line: 1 to 1

META TOPICPARENT	name="APPX510Features"

APPX Runtime Subroutine API

Line: 8 to 8

Overview

Changed:

<
<

>
>

Release 5.1.0 of the APPX Utility includes a new standardized designer API which can be used to gain access to extended functionality from within an APPX application. This API provides APPX Designers with a robust set of subroutines which can be called to do a variety of tasks. This API replaces the older subroutines that have been informally used, and all designers are encouraged to begin using the new subroutines.

General Information

All of these new subroutines are defined in the (---) application and begin with a period (.). They all use a standard call interface and use the same framework for returning resuts and reporting errors. They are grouped by name prefix so that related subroutines are grouped together by function. Data is passed into and returned from these subroutines by use of the PASS statement. Failure information is returned by use of a work field with the same name as the subroutine. This failure code field is tokenized so you can scan to see the failure reasons that can be returned.

Added:

>
>

If the subroutine accepts parameters (ie, READ, WRITE, APPEND to --- .STREAM OPEN), the parameters are case insensitive.

If the subroutine has required paremeters and you do not PASS the correct number of paremeters, the subroutine will issue a CANCEL identifying which parameter was missing.

General Subroutines

Utility Routines

.UTIL MOD SCROLL BEHAV

View topic | History: r59 < r58 < r57 < r56 | More topic actions...