XDialog Coded Listbox vs. Checkbox

[danh]

I took this from the Learning XDialog database where you use the '{{Data=value}' directive to code the listbox to set the value in a variable to one value, but to display another value.

The example in the lesson uses a listbox, but I have an instance where I would like to use it as a checkbox instead and cannot get it to work. I am including an attachment to show what I am talking about. If you run the script for the listbox and watch what shows up in the list below as you select entries, it is all correct. What I want is for it to do the same when you run the script for the checkbox. What shows up is the whole string, and not just the 'data' value.

Thanks for your help. Dan

[Tim Kiebert]

Re: XDialog Coded Listbox vs. Checkbox

I think this may be the nature of the check box. Depending on any other comments you get regarding this you might submit it as a bug. But the help pages regarding {data} speak of using it with List boxes and tree controls. ie, no mention of check boxes. It is weird though that the data displays properly in the checkbox control.

Here is a work around. (My changes in red)

dim clientlist as c
dim count as n
clientlist = table.external_record_content_get("clients","'{data='+customer_id+'}'+alltrim(lastname)+', '+alltrim(firstname)","lastname")
count = line_count(clientlist)
'dim a_selected[count] as c
dim a_select[count] as c
a_select.initialize(clientlist)

ui_dlg_box("Coded Check Boxes",<<%dlg%
{wrap=40}
{lf};
{justify=center}
Customer: \(sets the value of the 'customerId' variable);
[%M,O={@@}%.40,10customerId^$$a_select[B][COLOR=Red]!selectChange[/COLOR][/B]];
Actual value in the 'customerId' variable: ;
[%M%.40,10customerId];
\(if you type a different value in this text box the list box will reflect the different client);
{lf};
[COLOR=Red]Actual Customer Id pulled out of the  'customerId' variable using the *for_each\() function: ;
[%M%.40,10customerId2];[/COLOR]
{hyperlink=Show the actual data in the list box list!showdata};
{lf};
{justify=center}
<Close>;
%dlg%,<<%code%
'!select_client (end of Checkbox)
'^#a_selected    (end of textbox)
'if a_dlg_button = "select_client" then
'    a_dlg_button = ""
'    a_selected.clear()
'    a_selected.initialize(customerid)
'end if
[COLOR=Red]If a_dlg_button = "selectChange" then
    a_dlg_button = ""
    customerId2 = *for_each(x,word(word(x,2,"="),1,"}"),CustomerId)
end if[/COLOR]
if a_dlg_button = "showdata" then
    a_dlg_button = ""
    showvar(clientList)
end if
%code%)

You don't need to apply the conversion within the dialog if you don't need to display it there. Just do the conversion before you actually need to use the values.

[csda1]

Re: XDialog Coded Listbox vs. Checkbox

Hi Tim & Dan,

.... Depending on any other comments you get regarding this you might submit it as a bug.

I doubt it is a "bug" per say, just a limitation (but it's always a good wishlist item). While Alpha has a wide variety of functions and methods, one of my biggest complaints is illustrated here. Many functions do a feature or two, but don't carry it through all variations of usage to allow a consistency. The parameters to a function are sometimes overly complex (e.g. too many flags), or don't follow a logical pattern to allow dropping off the trailing parameters (which goes to a default), or have similar parameters to similar functions.

Recent trivial examples of this on the message board are Mod() not working 100% with decimals, and Round() not working with negative decimal positions. While not bugs per say as they worked beyond what Alpha might have concieved, neither were they trapped for invalid ranges of parameters. This kind of falls into the same.

Another example is that listview boxes (at least some variants - I don't recall precisely) can't (or didn't - Haven't really checked v9 in this respect) have an image in a row unless it is associated and in the 1st column. Why not any/every column ability to have images?

But the help pages regarding {data} speak of using it with List boxes and tree controls. ie, no mention of check boxes.

As above, it's not listed as a feature, but you would ideally expect a consistency

It is weird though that the data displays properly in the checkbox control.

I'm kind of surprised to, but apparently aspects of the same code do the same filtering.

Your solution was exactly right, with one possible, not common, exception. If you had a very big list (I suspect larger than you ever would want to have as a checkbox) , it might have been better (read as faster) to take the current line changed, and just change/add/delete that in the output list.

[Tim Kiebert]

Re: XDialog Coded Listbox vs. Checkbox

Hi Ira,

Glad you chimed in on this, thanks.
I think you put the issue very well. One of the key words I took from your reply is 'Consistency'. I guess what I described as weird is really a manifestation of inconsistency. Since the checkbox displays like similar controls do when supplying it with the same data one would expect the same output.

.....to take the current line changed, and just change/add/delete that in the output list.

Could you further explain what you mean by this. ( I am having one of my 'thick' moments.)

[csda1]

Re: XDialog Coded Listbox vs. Checkbox

Hi Tim,

Could you further explain what you mean by this. ( I am having one of my 'thick' moments.)

I guess it's just too late in the day for you there!:D

Anyway, you are updating the list, reprocessing the all the checked values each time there is a change. You could (and I'm not sure if you get just the row select number of the input - I think if the target is numeric type, it will, but assuming you can) take the row number from the list, and just add/delete or change that line in the output list (maybe a collection might work well for this), rather than using *for_each() to process the entire list. *for_each() is fast, but for a really big list still has to process a lot. Regex_merge() might be an alternative to *for_each()

[Tim Kiebert]

Re: XDialog Coded Listbox vs. Checkbox

I guess it's just too late in the day for you there!:D

And the couple of glasses of port may not be helping either. :D

But I see clearly now. Thanks

[danh]

Re: XDialog Coded Listbox vs. Checkbox

Thank you guys for the response. That is an interesting workaround. It works great.

One question, though, regarding the change, I want to use this in an embedded xdialog on a form and use variable binding to bind the result to a table field. So in essence, it needs to work in reverse, so it displays the result from the table field in view mode, if that makes sense. If you look again at the listbox, you can type in a valid customer ID in the bottom box, and it will automatically select the corresponding entry in the list. This needs to happen in order for it to work on an embedded xdialog on a form with variable binding, and it is not the case with the checkbox with the change. Is there a workaround for that...?? (:

[danh]

Re: XDialog Coded Listbox vs. Checkbox

The initial problem I posted here about the checkbox not working like the listbox has been identified by Selwyn as a bug, and should be fixed on the next release. It's this kind of service that keeps me believing in the product!

Selwyn gave me a workaround using another control (not sure the difference). That gave me my checkbox back, but it created another problem. It deletes the entry in the first record when the form is opened (which might be a bug, too), so you have to cancel changes in the OnInIt event to keep the entries intact. That seems to take care of the problem for now, but the bug fix will be better.

Attached is an updated example for those interested.

Thanks again for all your help!
Dan

[johnkoh]

Re: XDialog Coded Listbox vs. Checkbox

Tim,
Thank for this

If a_dlg_button = "selectChange" then
a_dlg_button = ""
customerId2 = *for_each(x,word(word(x,2,"="),1,"}"),CustomerId)
end if