xdialog closes form (it shouldn't)

[CALocklin]

Just wondering if anybody else has seen anything like this.

I have a form "A" with a child browse on it. I select a child record in the browse (call it record 2) and click a button to open form "B" to show details for that child record. From form "B" I open a modal xdialog and when the ui_dlg_box() command runs (checked in the debugger - it happens on that line), form "B" closes and I'm back to form "A" on child record #1. The xdialog is still open.

FWIW, both form "A" and "B" are opened with a simple form.view() - not as dialogs.

This worked perfectly in v9 and I haven't been able to find anything in the script that should cause this behaviour.

[G Gabriel]

Re: xdialog closes form (it shouldn't)

Don't have v10 and this sounds like an issue with v10 but, for diagnostic purposes, what happens if you change that xdlg to modeless instead? I am not suggesting that you should, just wondering.

[CALocklin]

Re: xdialog closes form (it shouldn't)

I should have known better than to ask a question like that before rebooting the computer. Apparently it was just the "tired computer" syndrome again. Sorry for wasting people's time.

Today it seems to be working correctly. Yesterday (or whenever I originally posted) I shut down A5 and tried again and the problem continued. Shutting down and rebooting the computer seems to have fixed it. (At least for now, I never trust anything long term when it comes to computers.):(

[Peter.Greulich]

Re: xdialog closes form (it shouldn't)

...
Today it seems to be working correctly. Yesterday (or whenever I originally posted) I shut down A5 and tried again and the problem continued. Shutting down and rebooting the computer seems to have fixed it. (At least for now, I never trust anything long term when it comes to computers.):(

One trick to try is to check task manager processes after you shut a5 down and see if Alpha5.exe is still running in the background. If so, kill it, and reload A5.

[CALocklin]

Re: xdialog closes form (it shouldn't)

Oh yeah! Go ahead; rub it in.

I actually knew that one, too, but didn't bother checking it.:o

I'm glad you pointed it out so others would know about it. It's a very useful thing to know - when you remember it.

OTHERS PLEASE NOTE: Peter is talking about the PROCESSES tab in the Task Manager - not the Applications tab. It amazes me how many people don't even realize there is a Processes tab. This is especially true of users (vs. developers). So, if you are trying to help someone over the phone, be aware of this and carefully walk them through the process of finding the Processes tab. I've learned that you have to ask them if they see the icons on the left - if they still do, then they haven't found the Processes tab.

[Clunes]

Re: xdialog closes form (it shouldn't)

While you are on the topic of funny things, I logged a bug sometime ago about disappearing styles in the xdialog genie. I found that when creating an xdialog and saving I would reopen to edit only to find the variables exist in the variable box, but the attached styles had completely disappeared. To get them back required shutting Alpha and reopening. I thought it a random thing but it seems to be happening more and more. I end upcoverting xbasic and doing the final work from there.

I have noted it on two computers with two different OS. I am presuming it may be a memory issue as I also get some random funny error after lots of work, when opening some codes with xdialogs saying cannot be created. It then opens OK.

I am starting to use more and more xdialogs for tasks. Does anyone else use a lot and have any subsequent operations problems, particularly across networks with multiple usesr etc. I am suspecting my novice knowldge of table access will get me into more lockouts when I go live with something.

[CALocklin]

Re: xdialog closes form (it shouldn't)

While you are on the topic of funny things, I logged a bug sometime ago about disappearing styles in the xdialog genie. I found that when creating an xdialog and saving I would reopen to edit only to find the variables exist in the variable box, but the attached styles had completely disappeared. To get them back required shutting Alpha and reopening. I thought it a random thing but it seems to be happening more and more. I end upcoverting xbasic and doing the final work from there.

I have noted it on two computers with two different OS. I am presuming it may be a memory issue as I also get some random funny error after lots of work, when opening some codes with xdialogs saying cannot be created. It then opens OK.

I have never actually used any styles but I did play with them once. However, in A5v9 I had problems (presumably memory problems - a.k.a., "random funny errors") that seemed to be related to opening and closing a lot of forms. As a result, I created a few xdialogs to use in place of some of the forms. This seemed to be an improvement but not a solution. Interestingly enough, I noticed in the release notes that Alpha has fixed a memory issue in forms in v10. I can't help thinking that the same issue existed in v9. In other words, have you tried recently to see if the "random funny errors" still occur? Maybe the form fix has solved the problem.

I am starting to use more and more xdialogs for tasks. Does anyone else use a lot and have any subsequent operations problems, particularly across networks with multiple usesr etc. I am suspecting my novice knowldge of table access will get me into more lockouts when I go live with something.

I use xdialogs quite a bit. However, I never use the xdialog genie anymore. I'm not sure if that matters as far as the stability so take it for whatever it's worth. Also, I mostly use the xdialogs for getting parameter input such as print parameters. I seldom use them for getting actual data that will be stored in the tables. I think regular forms are much easier for doing that.

I really have not had any problems with xdialogs themselves or with processes after the xdialog. I have learned that it is best to specifically close any tables opened in a script - whether there is an xdialog involved or not. Alpha says it tries to close all open tables when a script ends but note the word "tries". I have run into situations where a table was not closed for some reason so I now make sure that all "table.open()" commands are followed by a "<table_pointer>.close()" command before the script closes. And that could mean multiple 'close' commands if there are multiple places where the script/function could end.

Attached is one of the most complicated parameter input dialogs I have. (The xdialog is only 70 lines long but the complete "print" script is 1699 lines.) The thing I like about using xdialogs for getting this type of input (i.e., for "prompts") is that they have a unique look and the user gets used to the fact that something like this is probably prompting them for information about what to do next.

And, FWIW, it has amazed me how much the users prefer one parameter dialog vs. a series of dialogs prompting for individual items. I knew it would be better but I didn't expect people to rave over the improvement - but they did.

[Ton Spies]

Re: xdialog closes form (it shouldn't)

FWIW, it has amazed me how much the users prefer one parameter dialog vs. a series of dialogs prompting for individual items. I knew it would be better but I didn't expect people to rave over the improvement - but they did.

Hi Cal,

Two simple reasons to inspire confidence: conveniently arranged and a calmly act.
Prompting all the time causes disorder and confusion.

Some people then already know the sequence of questions and answer in advance without reading. And when they act wrong, (they say) it's your fault.

Nice example. and I prefer this one.:D

Ton