xdialog - one works, the other don't

[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.

[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

[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

[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

[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.

[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.

[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.

[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.