bb.donnay-software.com

might be a good idea. I try to implement it. Thank you

what is the elegant method to build a screen full of GETs, TABPAGES, ecc. and avoid the sequential display (slow refresh) of the objects that you are populating ? it would be possible to display an hourglass or a bitmap like 'wait...' in center of the drawingarea that hides the preparation of everyt...

however, a point does not seem to work without an external loop: "ENTER on last Get confirm all data, (same as Confirm button)" - using ENTEREXIT clause on DCREAD GUI if the user navigates between the GETS and arrives at the bottom of the GETs, the program must ask whether or not we want to record t...

since apparently it seems unsolvable my problem, tell me the correct way to insert the construction of the GET inside a my custom loop and make sure that at the end of DCREAD I can clean the memory and recreate the GET again? for example: DO WHILE .T. GetList := {} GetOptions:=NIL lExit:=.F. // recr...

Roger, when you have time, explain to me what happens when I leave the DCREAD loop with the SAVE clause ? "SAVE will save the GetList array after returning from the text or GUI reader. If the SAVE clause is not used, the GetList array will be re-initialized to an empty array." can I use the GetList ...

the trigger system works well, that's not the problem the most important problem is: what I do not understand on the example I wrote is the fact that at the first input of the DCREAD loop everything works correctly but when I exit with the SAVE clause from the loop and re-enter the DCREAD, the ENTER...

I know it looks a bit strange as I thought it ... the behavior I am trying to achieve is to follow this rule: the user starts by seeing the screen and the main buttons INS,MOD,DEL,VIEW, EXIT available by pressing exit, the program ends by pressing the other buttons, it enters input mode on the Gets ...

it is not easy for me to explain the reason for the necessary double loop. attached a small prg to test and what I try to make work: TEST.zip The dcread loop is used to manage the actions of the main buttons (INS,DEL,MOD,VIEW & EXIT); other buttons ( secondary ) are dedicate to SAVE & CANCEL action ...

to be able to create a continuous get loop that stops only with an exit button, do I have to use the SAVE clause in a DCREAD statement? --------------------------------------------------------- LOCAL GetOptions ,GetList := {} lExitKey:=.F. a:=b:=c:=d:=SPACE(10) @ 1,0 DCGET a GETOBJECT 1st_get @ 2,0 ...

this works properlyl

thanks Roger!