Description
If you have a long list of local procs in a form. Make a change to something in the middle/end. Compile, the cursor will go to the top of the trigger again. Would be much nicer if it stayed where it was.
Use Case
User is editing code. Compiles. Cursor goes to top of code instead of staying where it was.
Importance
Low
Type
Uniface 4GL
Operating System
Not Applicable
Status
Closed
This is unfortunately too big a change to implement in Uniface 9.
Uniface 10 uses a different code editor and this stays in the same position when you compile.
The people who joined our Uniface 10 workshops in Amsterdam and Las Vegas have seen this.
According to some (undocumented) features provided in 2006,
it seems to be a 5 line entry in the ADDITIONAL menu to achieve this usability.
start FLAME … well, this is one of the biggest change of the “new” IDE in Uniface 9… FLAME end
As we migrated to the latest Uniface and lab do not want to fix this bug, we found out a workaround… you have to *store* and then compile. It is still quite stupid, that cursor moves to the bottom of the screen, but at least it stays where it is. If you just compile, Uniface auto saves the code and teleports you to the top of the trigger.
Really, try saving before compiling, it might help you a lot.