On jeudi 11 décembre 2008, Benoit Minisini wrote:
I will post a fix so that when the Visible property of the form is set to
FALSE, the form is not shown at startup, but loaded. So the workaround
above will not be needed anymore!
Regards,
Fix committed in revision #1735.
Regards,
--
Perhaps the following ideas...
Every step in the wizard has an associated form for whatever it does for that
step.
Every form has a SUB for 'backwards' and 'forwards so that
when NEXT is clicked, the forwards code runs, which is whatever
is required for moving to the next form (ie: perform work,
Exactly.
The forward navigation depends on the user input, so it could jump
from Form1 to Form3 and then to Form2 ans do on...
So if we leave a footprint in the array, I think it *should* be easy
to reverse the process indeed sort of like an undo process.
But I'm not sure exactly what the best
Can you try to work a sample??
On Thu, Dec 11, 2008 at 3:04 PM, nando nand...@nothingsimple.com wrote:
To go back, you have to 'undo' all the things needed to properly go forward.
So, in form5 (ie step5) you would have code to run to 'undo' what you did to
get to step6...so when step6 has to
M0E Lnx a écrit :
Exactly.
The forward navigation depends on the user input, so it could jump
from Form1 to Form3 and then to Form2 ans do on...
So if we leave a footprint in the array, I think it *should* be easy
to reverse the process indeed sort of like an undo process.
But I'm not
I just can't seem to completely wrap my mind around this one.
It really doesn't matter if i return to the same state or not... as
long as I return there.
it gets complicated when for instance, you go in a sequence from 1, 2,
3 then you back up to 2... change something in 2 that now makes you
I found integer bug in gambas. Please try ?54*4100 in gambas
console. The result is negative, maybe because 4100 is converted
to integer rather than long integer. I can solve it by use manual
converting to ?54*clng(4100) but I think it should converted
automatically by interpreter,
