Syntax 1: For user objects of a known datatype – PB Docs 2017

Syntax 1: For user objects of a known datatype

Description

Opens a user object of a known datatype and stores a parameter in
the system’s Message object.

Applies to

Window objects and visual user objects

Syntax

Argument

Description

objectname

The name of the window or user object in which to
open the target user object.

targetobjectvar

The name of the target object you want to display.
You can specify a user object defined in the User Object painter
(which is a user object datatype) or a variable of the desired
user object datatype. OpenUserObject places a reference to the
opened target object in targetobjectvar.

parameter

The parameter you want to store in the Message
object when the target object is opened. Parameter must have one
of these datatypes:

  • String

  • Numeric

  • PowerObject

x (optional)

The x coordinate in PowerBuilder units of the
target object within the objectname object. The default is
0.

y (optional)

The y coordinate in PowerBuilder units of the
target object within the objectname object. The default is
0.

Return value

Integer. Returns 1 if it succeeds and -1 if an error occurs. If
any argument’s value is null, OpenUserObjectWithParm returns
null.

Usage

The system Message object has three properties for storing data.
Depending on the datatype of the parameter specified for
OpenUserObjectWithParm, scripts for the opened user object check one of
the following properties:

Message object property

Argument datatype

message.DoubleParm

Numeric

message.PowerObjectParm

PowerObject (PowerBuilder objects, including
user-defined structures)

message.StringParm

String

In the target user object, consider accessing the value passed in
the Message object immediately, because some other script may use the
Message object for another purpose.

Avoiding null object references

When you pass a PowerObject as a parameter, you are passing a
reference to the object. The object must exist when you refer to it
later or you get a null object reference, which causes an error. For
example, if you pass the name of a control on a window that is being
closed, that control will not exist when a script accesses the
parameter.

See also the usage notes for OpenUserObject, all of which apply
to OpenUserObjectWithParm.

Examples

This statement displays an instance of a user object named
u_Employee in the window w_emp and stores the string James Newton in
Message.StringParm. The Constructor event script for the user object
uses the string parameter as the text of a StaticText control
st_empname in the object. The script that opens the user object has the
following statement:

The target user object’s Constructor event script has the
following statement:

The following statements display an instance of a user object
u_to_open in the window w_emp and store a number in
message.DoubleParm:

See also

CloseWithReturn

OpenUserObject

OpenWithParm


Document get from Powerbuilder help
Thank you for watching.
Was this article helpful?
Subscribe
Notify of
guest
0 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x