Why does AppBuilder GUI compiler moves internal procedures (only with .wrx)? - Forum - OpenEdge Development - Progress Community

Why does AppBuilder GUI compiler moves internal procedures (only with .wrx)?

 Forum

Why does AppBuilder GUI compiler moves internal procedures (only with .wrx)?

This question is answered

Hi 

First time posting here.

Does someone know why the compiler moves internal procedures of GUI (.w) files which have an attached .wrx?

In my case - updated GUI object 'Enabled' flag which after a recompile moved an internal procedure.

Only applies when file has one or more OCX (Active X) files. 

Verified Answer
  • Hi Ivan,
     
    When you save a .w in the AppBuilder, it regenerates some parts of the code (i.e. the stuff it handles internally).  Your code is stored in temp-table records and then written out.  I am not sure why it would change the order of things, unless the .w was edited manually outside of the AppBuilder (not supported).
     
    If the AppBuilder is moving the procedures around to a different location after every save you should open a support case so we can look into it further.
     
    Brian

All Replies
  • Hi Ivan,
     
    When you save a .w in the AppBuilder, it regenerates some parts of the code (i.e. the stuff it handles internally).  Your code is stored in temp-table records and then written out.  I am not sure why it would change the order of things, unless the .w was edited manually outside of the AppBuilder (not supported).
     
    If the AppBuilder is moving the procedures around to a different location after every save you should open a support case so we can look into it further.
     
    Brian

  • Hi Brain,

    After your clarification this now makes sense why to internally handled code was getting moved around. Happens when different version program changes patched into each other via a comparison tool. Thanks one more time.

    Ivan

  • when i had issues like this i found opening and then immediately saving would produce consistent behaviour, so minimising erroneous diff creation. So i tended to do that before checking back into source control.