Xdialog issue with {condition_begin}

[EJR]

OK, I need help. I'm new at using xdialog, but I've jumped in with both feet and now I'm stuck. I trap CTRL-key sequences to toggle radio buttons and check boxes, but when I'm in a field that displays conditionally via {condition_begin} (such as one of the name fields at the top), the cursor disappears as soon as the CTRL-key sequence is pressed, but ui_dlg_ctl_current() indicates the cursor is still in the same field. If the cursor is in another field, it stays put (as I want). There are other issues I can live with and eventually figure out, but this one's vexing. Any help would be greatly appreciated!

Has anyone else run across this? It appears to be a bug. The script is attached.

Thanks,
Eric

[Clunes]

Re: Xdialog issue with {condition_begin}

This is impressive stuff. Really advance for me. Gave me a lot of ideas for my xdialog development. I not entirely sure what you want. My only thoughts here is you may achieve the same goals based on the field event rules. Xdialog field events operate on change, changing, killfocus etc. See help files. You may be able to combine what you do with those. When you use these a_dlg_ctl_goto() function will take you to where you want to go to every time.

[EJR]

Re: Xdialog issue with {condition_begin}

Thanks, Mark. I've been thinking more and more that my issue is a bug I need to report, so I'll do that. I haven't done anything with field rules, so I'll look into that to see if that helps. I can do all I want within forms and it should work, but I wanted to really learn xdialog and exercise its functionality to see what I could do with it. I still have a very long way to go...

[G Gabriel]

Re: Xdialog issue with {condition_begin}

Where do you expect to see the cursor?
If you use CTL-2 for instance, it will check the appropriate checkbox. Are you expecting to see it in the 2nd middle?
If so, you need to add a snippet of code to activate that control.
I don't see any bugs unless I am missing your question.

[EJR]

Re: Xdialog issue with {condition_begin}

Gabriel, thanks for jumping in. Run the xdialog and put the cursor in the first name field. Then, start editing "John" to "Jonathan" but -- then you realize this person has a second middle name, so you interrupt yourself and quickly press 'CTRL-2' to have the second middle name show, and then your cursor disappears.

I want the cursor to remain so I can finish editing the first name.

[G Gabriel]

Re: Xdialog issue with {condition_begin}

No Eric, it does not disappear. When you click CTL-2, the cursor activates the check box, that is, the focus shifts to the check box. If you want it to go back to the first name, you have to re-activate the first name control.

[EJR]

Re: Xdialog issue with {condition_begin}

But... try pressing CTRL-i or CTRL-a, and you'll see the check box for those will toggle but the control is not activated since the cursor remains in the field you are editing. That is the expected behavior, and that is what I want. Pressing the CTRL-key sequence does not activate the check box, from what I can tell.

Unless I'm missing something...

And thanks for spending time on this.

[G Gabriel]

Re: Xdialog issue with {condition_begin}

Eric:
Check THEN UNCHECK each one of these short cuts and see what happens.
I think what happens with these conditional controls is that alpha refreshes the xdlg based on the condition and thus the focus is lost.

[EJR]

Re: Xdialog issue with {condition_begin}

Gabriel,
I received a quick response to my bug report from Cian Chambliss and he gave me some ideas to work on. He mentioned that my code is 'hiding' the current control which causes the problem. You are right that the focus is lost. Cian gave me some ideas I'll build upon and try. I'll report back, hopefully with a work around to let me do what I wanted.

When you check/uncheck with the CTRL-key sequence, it reverts back and displays correctly. That tells me that somehow A5 thinks there are multiple versions of my name variables due to the {condition_begin} blocks. Food for thought...

[Davidk]

Re: Xdialog issue with {condition_begin}

Hi Eric,

I've had a look and tried to re-focus back to the fname control after pressing Ctrl-F etc.

If your cursor is in the First Name and Male is already select and then you press Ctrl-F, as you say the cursor disappears. Then, if you press Ctrl-M to select Male, focus is returned to the fname control. So I can see why you're asking about this... doesn't seem to make sense, but I don't have an answer.

I do have a question, however and ask with all humility because it is a great xdialog form... but why XDialog. As said, it's a great form, but so complicated. Could you not achieve the same with a normal form? Just curious as to why you decided on XDialog.

I don't do much with it 'cause it's so damn tough but I'd certainly use this form to demonstrate a number of different ideas.

And... what were the techniques suggested for getting around this problem?

[EJR]

Re: Xdialog issue with {condition_begin}

David,
Great question. Why xdialog? To learn. To be honest, this was my first xdialog and I wanted to see what I could do. A LONG, LONG TIME AGO I was a C/assembly language programmer, so I'm not afraid to jump in to complex things I know nothing about (that was me with xdialog as of the start of last week). I've learned xdialog forms might be quicker to create than regular forms (once you've figured out how to do them!), so my thinking is it will help me create solutions more quickly. And the best way for me to learn is to jump in head first without a safety net.

And as to the solution... I'm learning more and I think I jumped in deeper than planned! Apparently using {condition_begin} blocks can 'hide' controls, so I'm now looking at other solutions. I might have a partial solution later this evening. But, I actually think this is productive for me as I'm learning a lot about A5. But it's also possible I've stumbled into a real wall with xdialog on what I want to do here, but that's fine because I know I can do what I want with a form.

And for anyone wanting to try out xdialog, the best way is to simply jump in and do a little at a time. I've been working on this for just a week so far.

[Davidk]

Re: Xdialog issue with {condition_begin}

Well, that makes sense now. With a C/Assembly background you've got what it takes to get through XDialog. I dabled in assembler many, many years ago and just couldn't get it. Looking at XDialog makes my head hurt. I can understand what's written, but to write it... yikes. Thanks for the comments.

[Clunes]

Re: Xdialog issue with {condition_begin}

If I could add two cents worth on the value of xdialog instead of forms. If I have to create a new record, I will try to use an xdialog every time. I find it gives greater control over the user's actions. Nothing is saved until you want it to be and if the user walks away because of a dilbert distractionism, no other user is affected by status of the table. xdialog allows you create user workflows consistent with questions you need answered before moving on etc.

I find it much more easier to manage the xdialog, than control all the idiosyncracies of tables and fields on forms. that said they require a lot more work on the formatting view side of the house. One of my wish lists is for an xdialog form where you drag and move fields as you desire. The Form does it - VB does it - and quite a few other programs. Just need xdialog to do it.

[Davidk]

Re: Xdialog issue with {condition_begin}

I'd sure buy into XDialog more if there was an XDialog form. I always see the benefit of it, just need to take time for it.

[G Gabriel]

Re: Xdialog issue with {condition_begin}

This is not very complicated. It's pretty simple matter of fact. When you put a control in the xdlg that is based on a condition, whenever the condition changes alpha has to re-run the xdlg.
What does that mean?
It means whenever the condition changes the xdlg will re-run and the focus will go back to the object that receives initial focus. That's exactly what's happening but to your eyes it seems that the cursor "disappeared". It didn't, and there are no bugs. It's doing exactly what you are telling it to do.

So what's the solution?
1-Try an embedded xdlg instead of the conditional objects., or
2-Each time you get in a control, send it's name to a variable and when the xdlg reloads make that object the one with the initial focus.