Welcome!

Eclipse Authors: Lacey Thoms, Carmen Gonzalez, Liz McMillan, Ken Fogel, Jayaram Krishnaswamy

Related Topics: PowerBuilder, .NET

PowerBuilder: Article

The PostOpen Event – Why It Is So Important

PowerBuilder fundamentals

Normally I try to write applications on the DataWindow or Appeon but every now and then I get a question that makes me sit back and say, "Huh?"

In this case the question concerns the PostOpen event. I've seen that event named different things: ue_post_open, postOpen, post_open, ue_postOpen, etc. It has, as far as I can see, always had post and open in the name of the event. Further, just about every framework that I've ever seen has had that event in the base window.

The question that I was asked was, "Why is that event there?"

The programmer wanted to know why there was code in the post open and why was it not just put at the end of the open event? At first I was really confused by the question. It was like he was asking me why do we have arrays? I just couldn't imagine not knowing the answer.

Then it occurred to me that I learned the answer to that question from a book that was published almost 20 years ago. As far as I can tell there are no new books on PowerBuilder and there are only two print magazines, this one and the ISUG magazine.

That's it.

Further I came to think of the tremendous responsibility that the few PowerBuilder authors share. New PowerBuilder programmers turn to us for information and there aren't that many of us left writing. So that leaves a whole lot of PowerBuilder programmers who get all their training from reading the code of other programmers.

Often those other programmers were consultants who wrote the code ten years ago and worked for consulting firms that no longer exist.

To make a bad situation worse a lot of times those programmers are brave souls that have been recruited from other disciplines. When the company finds that their last PowerBuilder programmer has just quit because he got a much better offer they turn to their existing programming staff and ask who would like to pick up PowerBuilder. They may point out that there are 6 or 10 or, as in the case for one company for which I recently worked, 26 PowerBuilder programs that are all critical to the company. The PowerBuilder programmer would become indispensable to the company.

So suddenly a brave Visual Basic or Java programmer finds PowerBuilder installed on his machine. His boss pats him on his pointy little head and tells him that Google is his friend.

Where would you turn? If you picked up the mantle and offered to learn a language that you knew nothing about, what would you do? You'd turn to Amazon or Google. If you type "best PowerBuilder books" in Google the first mentioned is my Definitive DataWindow which was published 13 years ago and is embarrassingly out of date...and out of print.

Let's go to Amazon, there you will find the latest PowerBuilder book is for version 9. It was published 10 years ago. Since then... nothing.

Why should I be surprised that things that I find fundamental are entirely unknown by the newest PowerBuilder programmers.

Warning: If you are a seasoned PowerBuilder programmer the rest of this article will bore you silly.

There is an open event in a window. This is the event that happens when the window is "opened." Now the word ‘open' can be deceptive. A lot of people feel that a window is only opened when it is shown on the screen.

That would be wrong.

The open of a window begins when the open command is issued. That is to say, with a line like:

Open(w_client_editor)

The problem, the whole reason that a post open event is required goes all the way back to Microsoft Windows 3.0 Old Windows programmers will remember version 3.0 very well. Version 3.0 was almost the death of Microsoft Windows. It was unbearably slow. I am not exaggerating; it was the slowest version of Windows that was ever released.

It was so slow that Windows users were seriously studying what the impact of changing to another - any other - operating system would be.

This time Microsoft listened... and panicked. They did a study to determine what it is that makes the user perceive speed in an application. What could be changed to cause the user to believe that the application is faster with minimal real change to the operating system? It wasn't that Microsoft didn't want to address their problems with speed, they most certainly did, but addressing those problems would take time that Microsoft just didn't have. Microsoft was about to lose a lot of customers and once lost, it would be hard to get them back.

Microsoft learned that the visual perception strongly influenced the user's perception of speed. They learned that if the window POPPED onto the screen, all at once, even if the data wasn't there yet, then the users perceived speed. What killed the user perception was when they pressed a button and nothing happened for four seconds. The user would often punch that button two or three times. So Microsoft created operating system queues.

The graphics queue happened before the application queue. So graphics could be given a higher priority than the application and windows would paint faster. They released version 3.1 which was mostly just the addition of these queues (along with other changes like a floating point emulator in assembly code).

This was great but it broke the relationship of the open event with the code. This meant that you weren't guaranteed that everything would be created in the window until after the open event finishes.

Consider this code:

W_customer.open() event
Dw_1.setTransObject(sqlca)
Dw_1.retrieve()

This code would often result in a "Null object reference" error because dw_1 had not been created by Microsoft when the code ran.

Imagine how we felt when this happened. There was a null object reference in line 1 of the open event, but, but, but... that's dw_1. There it is, right there on the window! How can it be null? It's not dynamic. You put it there.

Okay, we learned that we should not put anything in the open event that referred to anything on the screen. Most of us learned to just not put anything at all in the open event except one line in the ancestor:

W_root.open() event
post event ue_post_open( )

For reasons already stated I imagine I can't rely on you knowing the difference between post event and trigger event or for that matter between postOpen and post open.

Okay, one at a time. Posting an event means that Microsoft Windows will open this window after the rest of the code in this script is executed. Basically it means, "Do this when you get a chance." So if you add that to the open event of your root window then it will call the ue_post_open event after all of the code in all of the descendants of this window is done.

Keep in mind the order of execution of events. First PowerBuilder goes to the farthest ancestor and then starts executing down the inheritance tree. If you have w_grandpa, and w_pa inherits from that and w_son inherits from that then the code in w_grandpa.open would execute first, then the code in w_pa, finally the code in w_son.

This means that if we put the post event in the open of w_grandpa, then the ue_post_open would happen after the last open event in the descendants. In our example:

W_grandpa.open->w_pa.open->w_son.open-> w_grandpa.ue_post_open-> w_son.ue_post_open->w_son.post_open

All that we have to do is create a ue_post_open event in our root window. We don't have to put anything in it, just create one. Then we post that event from the open event and we have a place now to put all our initialization code and don't have to worry about whether any object exists or not.

More important the screen will quickly draw or paint, giving the user the perception of speed. If you need to retrieve data and know it will take a short time, then you can set the pointer to an hourglass. I guarantee that your user will feel the window is faster.

I mentioned that most of us learned not to put anything in the open event. There is an exception to that rule. When your window is opened with a parameter then you should access the message object as the first line of code in your window.

Let me give you an example. Suppose that you open a window with a customer_id. You are going to use that customer_id as a parameter to the datawindow dw_1. Here is what you would do.

W_calling_window
Long ll_customer_id
Ll_customer_id = dw_detail.getItemNumber(dw_detail.getRow(), "customer_id")
openWithParm(w_customer_detail, ll_customer_id)

Now in the w_customer_detail window you need to set an instance variable. That's because we have just passed a variable to the new window and we are going to get it in the open event but we are going to retrieve the DataWindow in the ue_postOpen event. So let's do this. I will assume that you know how to declare an instance variable. Let's name it il_customer_id. Now let's look at the open event of w_customer_detail.

W_customer_detail.open()
il_customer_detail = message.longParm

Okay, now in the open event of w_customer_detail we have taken the longParm property of the global message object and put it in an instance variable.

Since we have inherited the w_customer_detail from whatever our base window is, the ue_postOpen event will automatically fire. That means that we don't have to fire off the event. Now I just have to put the code that we need in the window.

W_customer_detail.ue_postOpen()
dw_customer_info.setTransObject(sqlca)
dw_customer.retrieve(il_customer_detail)

Let's Do Some Housekeeping
I think that we've pretty well covered the post open event but in the process of doing that I've brought up a couple of other issues that I'd like to cover just to be complete.

First let's talk about post event as opposed to postEvent.

With the post event command you must know the name of the event that you want to post. You can pass the parameters normally. However, just like calling a function, the event has to exist and the parameters must be correct.

On the other hand the postEvent function takes a string as a parameter and that string is the name of the event. This means that you can store the name of the event in a table. In fact the event doesn't even have to exist. If it doesn't then nothing will happen. There will be no error thrown.

This makes the postEvent perfect for security systems where you can post an event based on a security role. Here is some code that might work for you in a menu event.

M_main.m_file.m_save.clicked
Datastore ld_security, ld_events
ld _secutity = create datastore
ld_events = create datastore

ld_events.dataobject = "d_events"
ld_security.dataobject = "d_get_security"

ld_events.setTransObject(sqlca)
ld_security.setTransObject(sqlca)

parentWindow.postEvent(ld_events.retrieve(ld_security.retrieve(gs_user_id)))

Using the postOpen function is very flexible but it is limited in the parameters that can be passed it. If you use the post event command, you can pass any number of parameters that you wish. The caveat is that the event must exist or you will get a compile time error. So the event that you used before for security cannot be done.

All that I just said for the postEvent and post event command applies also to the triggerEvent and trigger event commands.

Finally I'd like to mention the global message object.

This object is global. It can be accessed at any time by any other object. That means that if you access the message object in the postOpen event then another window may have changed your message object properties and this could corrupt what you are expecting.

Don't take this lightly. More than once I've debugged and found this error and believe me it is difficult to find. The problem is that it is not an error with logic or data but a timing error. These can be close to impossible to find.

Please take my word for this, make it a golden rule. If you open a window with a parameter, the first thing you do in the target or opened window is grab that value from the message object and store it.

Also, if you do a closeWithReturn then you need to immediately get the value from the message object.

There you have it. I've covered in some detail some basic information that might not be so easily learned any more.

More Stories By Richard (Rik) Brooks

Rik Brooks has been programming in PowerBuilder since the final beta release before version 1. He has authored or co-authored five books on PowerBuilder including “The Definitive DataWindow”. Currently he lives in Mississippi and works in Memphis, Tennessee.

Comments (1) View Comments

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


Most Recent Comments
ywerde 02/20/13 04:14:00 PM EST

In your introduction you clearly state the problem new PowerBuilder developers face when they find the IDE installed on their machine. You then go on to talk about the lack of current training materials.
One important cost effective training resource you omitted is the online training from ISUG/eLearnIT. Everyone can learn more here.

@ThingsExpo Stories
Software AG helps organizations transform into Digital Enterprises, so they can differentiate from competitors and better engage customers, partners and employees. Using the Software AG Suite, companies can close the gap between business and IT to create digital systems of differentiation that drive front-line agility. We offer four on-ramps to the Digital Enterprise: alignment through collaborative process analysis; transformation through portfolio management; agility through process automation and integration; and visibility through intelligent business operations and big data.
There will be 50 billion Internet connected devices by 2020. Today, every manufacturer has a propriety protocol and an app. How do we securely integrate these "things" into our lives and businesses in a way that we can easily control and manage? Even better, how do we integrate these "things" so that they control and manage each other so our lives become more convenient or our businesses become more profitable and/or safe? We have heard that the best interface is no interface. In his session at Internet of @ThingsExpo, Chris Matthieu, Co-Founder & CTO at Octoblu, Inc., will discuss how these devices generate enough data to learn our behaviors and simplify/improve our lives. What if we could connect everything to everything? I'm not only talking about connecting things to things but also systems, cloud services, and people. Add in a little machine learning and artificial intelligence and now we have something interesting...
Last week, while in San Francisco, I used the Uber app and service four times. All four experiences were great, although one of the drivers stopped for 30 seconds and then left as I was walking up to the car. He must have realized I was a blogger. None the less, the next car was just a minute away and I suffered no pain. In this article, my colleague, Ved Sen, Global Head, Advisory Services Social, Mobile and Sensors at Cognizant shares his experiences and insights.
We are reaching the end of the beginning with WebRTC and real systems using this technology have begun to appear. One challenge that faces every WebRTC deployment (in some form or another) is identity management. For example, if you have an existing service – possibly built on a variety of different PaaS/SaaS offerings – and you want to add real-time communications you are faced with a challenge relating to user management, authentication, authorization, and validation. Service providers will want to use their existing identities, but these will have credentials already that are (hopefully) irreversibly encoded. In his session at Internet of @ThingsExpo, Peter Dunkley, Technical Director at Acision, will look at how this identity problem can be solved and discuss ways to use existing web identities for real-time communication.
Can call centers hang up the phones for good? Intuitive Solutions did. WebRTC enabled this contact center provider to eliminate antiquated telephony and desktop phone infrastructure with a pure web-based solution, allowing them to expand beyond brick-and-mortar confines to a home-based agent model. It also ensured scalability and better service for customers, including MUY! Companies, one of the country's largest franchise restaurant companies with 232 Pizza Hut locations. This is one example of WebRTC adoption today, but the potential is limitless when powered by IoT. Attendees will learn real-world benefits of WebRTC and explore future possibilities, as WebRTC and IoT intersect to improve customer service.
From telemedicine to smart cars, digital homes and industrial monitoring, the explosive growth of IoT has created exciting new business opportunities for real time calls and messaging. In his session at Internet of @ThingsExpo, Ivelin Ivanov, CEO and Co-Founder of Telestax, will share some of the new revenue sources that IoT created for Restcomm – the open source telephony platform from Telestax. Ivelin Ivanov is a technology entrepreneur who founded Mobicents, an Open Source VoIP Platform, to help create, deploy, and manage applications integrating voice, video and data. He is the co-founder of TeleStax, an Open Source Cloud Communications company that helps the shift from legacy IN/SS7 telco networks to IP-based cloud comms. An early investor in multiple start-ups, he still finds time to code for his companies and contribute to open source projects.
The Internet of Things (IoT) promises to create new business models as significant as those that were inspired by the Internet and the smartphone 20 and 10 years ago. What business, social and practical implications will this phenomenon bring? That's the subject of "Monetizing the Internet of Things: Perspectives from the Front Lines," an e-book released today and available free of charge from Aria Systems, the leading innovator in recurring revenue management.
The Internet of Things will put IT to its ultimate test by creating infinite new opportunities to digitize products and services, generate and analyze new data to improve customer satisfaction, and discover new ways to gain a competitive advantage across nearly every industry. In order to help corporate business units to capitalize on the rapidly evolving IoT opportunities, IT must stand up to a new set of challenges.
There’s Big Data, then there’s really Big Data from the Internet of Things. IoT is evolving to include many data possibilities like new types of event, log and network data. The volumes are enormous, generating tens of billions of logs per day, which raise data challenges. Early IoT deployments are relying heavily on both the cloud and managed service providers to navigate these challenges. In her session at 6th Big Data Expo®, Hannah Smalltree, Director at Treasure Data, to discuss how IoT, Big Data and deployments are processing massive data volumes from wearables, utilities and other machines.
All major researchers estimate there will be tens of billions devices – computers, smartphones, tablets, and sensors – connected to the Internet by 2020. This number will continue to grow at a rapid pace for the next several decades. With major technology companies and startups seriously embracing IoT strategies, now is the perfect time to attend @ThingsExpo in Silicon Valley. Learn what is going on, contribute to the discussions, and ensure that your enterprise is as "IoT-Ready" as it can be!
P2P RTC will impact the landscape of communications, shifting from traditional telephony style communications models to OTT (Over-The-Top) cloud assisted & PaaS (Platform as a Service) communication services. The P2P shift will impact many areas of our lives, from mobile communication, human interactive web services, RTC and telephony infrastructure, user federation, security and privacy implications, business costs, and scalability. In his session at Internet of @ThingsExpo, Erik Lagerway, Co-founder of Hookflash, will walk through the shifting landscape of traditional telephone and voice services to the modern P2P RTC era of OTT cloud assisted services.
While great strides have been made relative to the video aspects of remote collaboration, audio technology has basically stagnated. Typically all audio is mixed to a single monaural stream and emanates from a single point, such as a speakerphone or a speaker associated with a video monitor. This leads to confusion and lack of understanding among participants especially regarding who is actually speaking. Spatial teleconferencing introduces the concept of acoustic spatial separation between conference participants in three dimensional space. This has been shown to significantly improve comprehension and conference efficiency.
The Internet of Things is tied together with a thin strand that is known as time. Coincidentally, at the core of nearly all data analytics is a timestamp. When working with time series data there are a few core principles that everyone should consider, especially across datasets where time is the common boundary. In his session at Internet of @ThingsExpo, Jim Scott, Director of Enterprise Strategy & Architecture at MapR Technologies, will discuss single-value, geo-spatial, and log time series data. By focusing on enterprise applications and the data center, he will use OpenTSDB as an example to explain some of these concepts including when to use different storage models.
SYS-CON Events announced today that Gridstore™, the leader in software-defined storage (SDS) purpose-built for Windows Servers and Hyper-V, will exhibit at SYS-CON's 15th International Cloud Expo®, which will take place on November 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA. Gridstore™ is the leader in software-defined storage purpose built for virtualization that is designed to accelerate applications in virtualized environments. Using its patented Server-Side Virtual Controller™ Technology (SVCT) to eliminate the I/O blender effect and accelerate applications Gridstore delivers vmOptimized™ Storage that self-optimizes to each application or VM across both virtual and physical environments. Leveraging a grid architecture, Gridstore delivers the first end-to-end storage QoS to ensure the most important App or VM performance is never compromised. The storage grid, that uses Gridstore’s performance optimized nodes or capacity optimized nodes, starts with as few a...
The Transparent Cloud-computing Consortium (abbreviation: T-Cloud Consortium) will conduct research activities into changes in the computing model as a result of collaboration between "device" and "cloud" and the creation of new value and markets through organic data processing High speed and high quality networks, and dramatic improvements in computer processing capabilities, have greatly changed the nature of applications and made the storing and processing of data on the network commonplace. These technological reforms have not only changed computers and smartphones, but are also changing the data processing model for all information devices. In particular, in the area known as M2M (Machine-To-Machine), there are great expectations that information with a new type of value can be produced using a variety of devices and sensors saving/sharing data via the network and through large-scale cloud-type data processing. This consortium believes that attaching a huge number of devic...
Innodisk is a service-driven provider of industrial embedded flash and DRAM storage products and technologies, with a focus on the enterprise, industrial, aerospace, and defense industries. Innodisk is dedicated to serving their customers and business partners. Quality is vitally important when it comes to industrial embedded flash and DRAM storage products. That’s why Innodisk manufactures all of their products in their own purpose-built memory production facility. In fact, they designed and built their production center to maximize manufacturing efficiency and guarantee the highest quality of our products.
All major researchers estimate there will be tens of billions devices - computers, smartphones, tablets, and sensors - connected to the Internet by 2020. This number will continue to grow at a rapid pace for the next several decades. Over the summer Gartner released its much anticipated annual Hype Cycle report and the big news is that Internet of Things has now replaced Big Data as the most hyped technology. Indeed, we're hearing more and more about this fascinating new technological paradigm. Every other IT news item seems to be about IoT and its implications on the future of digital business.
Can call centers hang up the phones for good? Intuitive Solutions did. WebRTC enabled this contact center provider to eliminate antiquated telephony and desktop phone infrastructure with a pure web-based solution, allowing them to expand beyond brick-and-mortar confines to a home-based agent model. Download Slide Deck: ▸ Here
BSQUARE is a global leader of embedded software solutions. We enable smart connected systems at the device level and beyond that millions use every day and provide actionable data solutions for the growing Internet of Things (IoT) market. We empower our world-class customers with our products, services and solutions to achieve innovation and success. For more information, visit www.bsquare.com.
With the iCloud scandal seemingly in its past, Apple announced new iPhones, updates to iPad and MacBook as well as news on OSX Yosemite. Although consumers will have to wait to get their hands on some of that new stuff, what they can get is the latest release of iOS 8 that Apple made available for most in-market iPhones and iPads. Originally announced at WWDC (Apple’s annual developers conference) in June, iOS 8 seems to spearhead Apple’s newfound focus upon greater integration of their products into everyday tasks, cross-platform mobility and self-monitoring. Before you update your device, here is a look at some of the new features and things you may want to consider from a mobile security perspective.