Getting Started-JetNet

After an application's basic functionality is in place, you typically continue to work on it to fine tune its behavior and usability. This lesson shows how to:

• Define a hook that handles double-click events. In this lesson, double-clicking in a grid row calls a procedure that opens a screen and sends the row data to it.

• Write a JPL procedure that executes a database query conditionally.

  ---

1. If necessary:

   • Reactivate your application, invoke the editor, and connect to the middleware.

   • Reopen the dstslect.scr and dstord.scr client screens from client.lib on the application server.

A widget's Double-click property can be set to a control string that determines what happens when users double-click on that widget. In this lesson, you edit the client screen dstslect.scr to control what happens when a user double-clicks on a distributor record in the grid widget. The grid widget columns' Double-click property is set to call the send_dst_data procedure, which displays the selected distributor's record for editing. Thus, double-clicking on any grid widget field emulates the behavior of the Orders button (described in lessons 12 and 13).

2. Bring focus to the dstslect.scr client screen and in the grid widget, select widgets distrib_id, distrib_name, and phone by selecting grid columns Distrib_id, Distributors, and Phone columns:

   • Windows Shift+click on the column titles.

   • Motif Shift+click directly within a cell in each column.
     

3. Under Validation, set these widgets' Double Click property to ^send_dst_data("SELECT").

   When the user double-clicks in any of the columns in the grid widget, the send_dst_data procedure executes (as it also does when the Orders push button is chosen) and sends the selected ID to the dstord.scr client screen.

4. Bring focus to the dstord.scr client screen and select all the columns in the grid widget.
5. Under Validation, set the Double Click property to ^send_order_data().

   When the user double-clicks on a specific order, the send_order_data procedure, which is associated with the dstord.scr screen, is called. This procedure is described later (page 16-20).

6. Save all open screens (press F6).

When you edit an existing distributor's data or add a distributor on the dstord.scr (Distributor Orders) screen, it is not immediately visible when you return to the dstslect.scr (Select Distributor) screen. You can enhance the screen entry procedure on the dstslect.scr client screen so that when the screen redisplays (after the Distributor Orders screen closes), a View command automatically executes. This causes the updated database records to redisplay.

7. If necessary, reopen the JPL edit window for the dstslect.scr client screen:

   • Select the dstslect.scr client screen (deselect all widgets).

   • Under Focus, select the JPL Procedures property.

8. In the JPL edit window, delete the screen wizard screen entry procedure—everything up to the send_dst_data procedure.
9. Get the new screen entry procedure from the tutorial library:

   • Choose EditInsert From Library. The Open JPL Module dialog opens.

   • If necessary, open tutorial.lib by choosing Open and selecting it from the Open Library dialog.

   • From the Open JPL Module dialog, select tutorial.lib and select se_slect.jpl from its list of members. Choose OK.
     

     The enter_screen procedure for the dstslect.scr client screen is read into the JPL Program text window.

     proc enter_screen (screen_name, context)
     {
     	public smwizard.jpl
     	if (K_EXPOSE & context)
      	{
     		if (sm_tm_command("VIEW")!=0)
     		return 1
     	}
     	return 0
     }

     The expression in the if statement tests the K_EXPOSE bit in the context argument. If the expression evaluates to true (the screen was reexposed), the View command executes and the updated database records are displayed. Otherwise, the procedure returns without performing any actions.

10. Save the procedure: choose FileSave.

Now when you add or edit a distributor record, those changes should display immediately after you return to the Select Distributor screen.

11. Bring focus to the dstslect.scr client screen.
12. Choose FileTest Mode or .

The Select Distributor screen opens.

13. Enter M in the Distributor field and choose .

All distributors having an uppercase M in their name are displayed, including the one you added in Lesson 13.

14. Double-click anywhere on the Movie Time row.

    The Distributor Orders screen opens, overlaying the Select Distributor screen.

    

15. Enter (555) 345-6000 in the Phone field and choose Save.
16. Close the Distributor Orders screen (choose Close from the system menu).

    The Select Distributor screen regains focus. The phone number shows the new data that you just saved to the vidsales database.

17. Return to the editor when you're done. Remember to save your screens (FileSave All).

    ---

You enhanced the user interface by performing these tasks:

• Implemented double-click events. Now in addition to choosing push buttons, a user can invoke the send_dst_data procedure by double-clicking on a specific distributor record on the Select Distributor screen. This action invokes the procedure and sends the selected ID to the Distributor Orders screen.

• Wrote a screen entry procedure for the dstslect.scr client screen that executes only when the screen is reexposed.

What did you learn?

You learned:

• Double-click events are a useful enhancement to the user interface.

• Screen entry procedures can force a database transaction command to be issued without requiring any input from the user.