Project

General

Profile

Bug #3096

Bug #2677: fix drawing and functional differences between P2J GUI and 4GL GUI

Mnemonics highlighting for buttons in GUI

Added by Vadim Gindin almost 8 years ago. Updated almost 8 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
05/04/2016
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:

History

#1 Updated by Vadim Gindin almost 8 years ago

This task is about implementation of logic that shows/hides mnemonics for buttons in GUI.

Proposal. Behaviour is strange and it looks like PROGRESS saves some information between different runs of the same procedure, but I would prefer it would be wrong, because it is illogically.

Lets assume we have the following test:

def button btn1 label "To&yota".
def button btn2 label "D&odge".
def button btnex label "Exit".

def frame frame1 btn1 btn2 btnex.
enable all with frame frame1.
wait-for choose of btnex.

Here are 2 mnemonics defined for buttons: "y" for "Toyota" and "o" for "Dodge".

  1. First run. Mnemonics aren't shown. I press ALT and mnemonics become visible (letters are underlined). I close the window.
  2. Second run. Mnemonics are shown right after start. For all sequenced runs mnemonics will be shown.
  3. If I run the test from command line and switch to some other window before the test window will appear, then buttons mnemonics will not be highlighted. I.e. the sequence is the following:
    1. Run the command prowin32 -p "btn_mnem.p"
    2. Switch to other OS window, for example to Explorer.
    3. The test window is opened with buttons mnemonics not highlighted.

#2 Updated by Greg Shah almost 8 years ago

Did you test this using the "procedure editor"? That would explain your results, since state can be left around.

NEVER test using the procedure editor. Always pass the -p program_filename on the prowin32.exe command line.

#3 Updated by Vadim Gindin almost 8 years ago

Greg Shah wrote:

Did you test this using the "procedure editor"? That would explain your results, since state can be left around.

NEVER test using the procedure editor. Always pass the -p program_filename on the prowin32.exe command line.

I remember that. I'm testing using only command line utility. May be it is just the logic I still didn't understand..

#4 Updated by Vadim Gindin almost 8 years ago

More: if I have 2 dynamic windows created at start time, i.e. one of them is active and one of them is inactive, behaviour is the same for both windows: the same as for single window (first run: not highlighted and second run and all sequenced runs: highlighted).

Also available in: Atom PDF