xdialog - one works, the other don't

[johnkoh]

Re: xdialog - one works, the other don't

G,

I agreed with you and this

The event name ( Red color ) should not using the Reserved names, -- See Event Syntax for Reserved name.

is wrong statement.

Thank you.

[G Gabriel]

Re: xdialog - one works, the other don't

Peter,

From your first event case;

The event name ( Red color ) should not using the Reserved names, -- See Event Syntax for Reserved name.




This is working for me

 If a_dlg_button = "empSelect_change[COLOR="#FF0000"][SIZE=5]d[/SIZE][/COLOR]"  	
	getEmployee()
			
	a_dlg_button = ""
End if

John/Peter/Al:
Posterity bound:
change is also an xdlg event.
Change and changed are both legitimate xdlg events. The difference is when each fires.

[Al Buchholz]

Re: xdialog - one works, the other don't

if I can add one more thing to posterity of this thread.

use either debug(1) or write to the trace window to follow exactly what is happening - rather than what you expect to happen.

Within a killfocus, only write the trace window since calling debug(1) will call the killfocus again and you'll get caught in loopy land.

[Peter.Greulich]

Re: xdialog - one works, the other don't

Thanks John. Glad you pointed that out. Actually I already changed that one on general principles, but I have another one I'll have to check.

[johnkoh]

Re: xdialog - one works, the other don't

Peter,

From your first event case;

The event name ( Red color ) should not using the Reserved names, -- See Event Syntax for Reserved name.

If a_dlg_button = "empSelect_change"
getEmployee()

a_dlg_button = ""
End if

This is working for me

 If a_dlg_button = "empSelect_change[COLOR="#FF0000"][SIZE=5]d[/SIZE][/COLOR]"  	
	getEmployee()
			
	a_dlg_button = ""
End if

[Ray in Capetown]

Re: xdialog - one works, the other don't

Peter following this thread with interest (not that I understand much of the esoteric combinations of this dlg code) I call my dlg coding "poke around and try again"
I have spent almost as many days on a multi data list dialog to improve the user data capture speed and experience (seconds) as I followed you work on your time machine.
Yesterday I delivered a revolutionised (well I think so) status logging method that is now tight, compact and comprehensive with mm of mouse movement.
1. the users hardly notice as they shoot through many more captures per minute without mistakes than with their previous system
2. the more time you spend and the smoother it operates the less it is appreciated
3. you will likely not be charging for the additional days spent beyond just having it work (For that simple thing? whats the big deal)

Is it martyrdom? no definitely not, purism, perfectionism and dedication ? a fair amount, accolades? very little
Satisfaction !!!
Keep these coming it's just flippin' inspirational.

I tell clients its easy to write a complicated application much harder to make it simple
I will change my byline when I get the chance

[Peter.Greulich]

Re: xdialog - one works, the other don't

Thanks Stan & Al.

Yeah, that was the problem. I had

If a_dlg_button = "empSelect_change"  	
	getEmployee()
			
	a_dlg_button = ""
End if

in the code section. It didn't occur to me that other events might fire.

This fixes it, of course:

If left(a_dlg_button,10) = "empSelect_"
	If a_dlg_button = "empSelect_change"
		getEmployee()
	End if
	
	a_dlg_button = ""
End if

[Al Buchholz]

Re: xdialog - one works, the other don't

So you're saying the killfocus event is a killjoy?

I've called it a variety of things including a kill joy. But we'll leave it at that.

[Stan Mathews]

Re: xdialog - one works, the other don't

So you're saying the killfocus event is a killjoy?

[Al Buchholz]

Re: xdialog - one works, the other don't

Sometimes it's like a bad penny, it just won't go away....

On the other hand generating events especially the killfocus one creates another caveat that is easy to become circular. And a ton of fun.

[Stan Mathews]

Re: xdialog - one works, the other don't

Thanks for the clarification on the modeless xdialog, Al.

One could also

,<<%code%
if a_dlg_button = "Close" then
    'do nothing - the dialog will close
else if left(a_dlg_button,10) = "empSelect_"
       'code here to process the possible events in a select...case...end select structure
else
    msgbox(a_dlg_button)
    a_dlg_button = ""
end if
%code%)

[Al Buchholz]

Re: xdialog - one works, the other don't

Well, yes, that solves it. And yes, why?

Because the field (vEmps) has the

!empSelect_*

which generates the events for the field making a_dlg_button <> "" thereby closing a ui_dlg_box.

But that leaves open a ui_modeless_dlg_box by definition is modeless and needs to be forced to close.

Use debug(1) at the start of Stan's event code to follow the execution.

Using the * to generate events may generate more events than needed and then need to be defined so they can be handled or filtered out if not needed.

(edit: I have to type faster and test less.. ;) at least to get ahead of Stan.)

[Stan Mathews]

Re: xdialog - one works, the other don't

Ok, answer is, I think, you have an event defined for the vemps variable.

[%dk%.96,41 index^"Emp ID:13|Last Name:25|First Name:20|Badge No:18|Status:17"vEmps!empSelect_*] ;;;

In a normal modal xdialog anything that sets a_dlg_button to a value other than "" closes the xdialog. As soon as the vemps variable receives focus the empselect_setfocus event fires and that is placed in a_dlg_button. Since the event is not handled that closes the xdialog.

Change to

,<<%code%
if a_dlg_button = "Close" then
    'do nothing - the dialog will close
else
    msgbox(a_dlg_button)
    a_dlg_button = ""
end if
%code%)

to observe.

[Peter.Greulich]

Re: xdialog - one works, the other don't

Well, yes, that solves it. And yes, why?

[Stan Mathews]

Re: xdialog - one works, the other don't

And tacking this on the end makes it work. I have a feeling you'rd rather know why than just find a fix.

,<<%code%
if a_dlg_button = "Close" then
    'do nothing - the dialog will close
else
    a_dlg_button = ""
end if
%code%)