Step 3: Declare native classes and global functions – PB Docs 125
Step 3: Declare native classes and global functions For each native class that the nonvisual extension supports, declare an ANSI C++ class that inherits from IPBX_NonVisualObject, which is the ancestor class for all nonvisual PowerBuilder native classes. The declaration of the class can be placed in a header file, and it must include Invoke and…
Edit Mask edit style (code 90) – PB Docs 125
Edit Mask edit style (code 90) Table A-18 shows a sample row in the PBCatEdt table for an EditMask edit style. Table A-19 shows the meaning of the values in Table A-18. About the example This example shows an Edit Mask edit style using a code table of display and data values as part of…
Creating a new TreeView DataWindow – PB Docs 125
Creating a new TreeView DataWindow You use the TreeView wizard and the DataWindow painter to create a TreeView DataWindow. Document get from Powerbuilder help Thank you for watching.
Monitoring the call stack – PB Docs 125
Monitoring the call stack The Call Stack view shows the sequence of function calls leading up to the script or function that was executing at the time of the breakpoint. Each line in the Call Stack view displays the name of the script and the line number from which the call was made. The yellow…
Using a window – PB Docs 125
Using a window You can create a window that is similar to the Profiling tab on the System Options dialog box and add it to any application that is under development, so that you can start and stop tracing when testing specific actions. The w_starttrace window is available in the PowerBuilder Profiler sample in the…
Debugging windows opened as local variables – PB Docs 125
Debugging windows opened as local variables One way to open a window is by declaring a local variable of type window and opening it through a string. For example:
1 |
window mywin<br>string named_window<br>named_window = sle_1.Text<br>Open(mywin, named_window) |
The problem Normally, you cannot debug windows opened this way after the script ends because the local variable (mywin in the preceding script) goes out…
Selecting templates at runtime – PB Docs 125
Selecting templates at runtime Two DataWindow properties, Export.XML.TemplateCount and Export.XML.Template[ ].Name, enable you to provide a list of templates from which the user of the application can select at runtime. The TemplateCount property gets the number of templates associated with a DataWindow object. You can use this number as the upper limit in a FOR…
Exporting to XML – PB Docs 125
Exporting to XML You can export the data in a DataWindow or DataStore object to XML using any of the techniques used for exporting to other formats such as PSR or HTML: Using the SaveAs method:
1 |
ds1.SaveAs("C:TEMPTemp.xml", Xml!, true) |
Using PowerScript dot notation or the Describe method:
1 |
ls_xmlstring = dw1.Object.DataWindow.Data.XMLls_xmlstring = dw1.Describe(DataWindow.Data.XML) |
Using the Save Rows As menu item in the…
Adding and deleting TreeView levels – PB Docs 125
Adding and deleting TreeView levels You add and delete TreeView levels using the Rows menu in the DataWindow painter. To create an additional level in a TreeView DataWindow: Open the TreeView DataWindow if it is not already open. Select Rows>Create TreeView Level from the menu bar. The Specify Group Columns dialog box displays. Specify the…
Attributes – PB Docs 125
Attributes Controls or expressions can also be referenced for element attribute values. Select Edit/Add Attribute from the pop-up menu for elements to edit an existing attribute or add a new one. For each attribute specified, you can select a control reference from the drop–down list or enter a literal text value. A literal text value…