Quantcast
Channel: SCN : All Content - PowerBuilder Developer Center
Viewing all articles
Browse latest Browse all 2935

Anomaly in Menu Source Code. What's the cause and the cure?

$
0
0

As I read through the menu source code (painter generated) of a massive, 20 yr. old, application’s large frame menu (35971 bytes in size) I am noticing a certain weirdness who’s origin I can’t determine but whose presence may be affecting it's ability to batch compile using PowerGen

 

First the observation:

 

The vast majority of menu item events have their clicked script at the end of their definition. Here is one example:

menuscript01.png

 

 

However a minority of menu scripts have their clicked event defined at the top of their definition. Here is an example showing it (note the event above it has it’s clicked event defined at the end of its definition)

 

menuscript02.png

A while back a developer attempted to build the application using PowerGen (I have not yet attempted this build)

 

 

The Menu did compile.  This was the error message

 

m_frame  D:\BUILD\menu.pbl (0003):  Error       C0113: Error reading object source entry: m_frame.srm

 

----------------

Four questions:

1) Have you ever seen anything like this before?

2) What happened to the menu source code?  Why is the clicked event occasionally defined in the 'wrong' place

3) What is the long term impact of this 'hybrid' source code?

4) Should the menu be totally rebuild from scratch?

 

TIA

Yakov


Viewing all articles
Browse latest Browse all 2935

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>