3 replies to this topic

[Tyleulen]

I have run into a couple of "features" and I am left scratching my head.

I have a combo box that calls a global screen to allow the user to search. The problem arrises in that ProIV seems to have a "feature" that even though the global screen has no parameters, and there is no map associated with the combobox, it still trys to "help" by starting the screen scrolled down the list to where the default value is. So, since the default is 'ALL' and the data is mostly numeric, it displays the bottom of the list instead of the top.

In my effort to get around this "feature" I altered the logic so that it nulls the field On Focus, then restores the default value in Lost Focus if it is still null. This works ok as a cludge, my list now displays from the top, but it introduces a new problem: If the user shift-tabs through the field it executes the On Focus logic, but not the Lost Focus logic! So, the user can leave the field blank. If I mark the field as Must Input then the Lost Focus logic never gets updated and you get stuck in the field.

So, is there any way to suppress the "feature" that trys to sort the list, or is there anyway to force the Lost Focus logic to execute on a shift-tab?

At this point, I am considering leaving the default set to null and just have a display only field over the top of the actual input field that says 'ALL' Please tell me there is a better answer.

Edit: ProIV version 5.5b524
VIP version 5.5923

Edited by Tyleulen, 06 August 2008 - 05:59 PM.

[andykay]

You've probably already tried this, but I'll ask anyways...Have you tried controlling the start position with @SPSEQ?


AK

[Tyleulen]

You've probably already tried this, but I'll ask anyways...Have you tried controlling the start position with @SPSEQ?


AK

Since it is calling a global function with no parameters/map setting @SPSEQ doesn't seem to do any good. Since the search global is attached to screens all over the system I don't want to have to alter it to require a start point and then have to fix all the calling funtions.

My current cludge is to have the default set to ' ALL' and then twiddle with the justification to get it to almost line up with the other fields. Since the first character is now a space, it starts at the top of the list. But it still looks hackneyed to me. I am a little flabergasted that shift-tabbing out of a field skips the lost focus logic.

[DARREN]

You've probably already tried this, but I'll ask anyways...Have you tried controlling the start position with @SPSEQ?


AK

Since it is calling a global function with no parameters/map setting @SPSEQ doesn't seem to do any good. Since the search global is attached to screens all over the system I don't want to have to alter it to require a start point and then have to fix all the calling funtions.

My current cludge is to have the default set to ' ALL' and then twiddle with the justification to get it to almost line up with the other fields. Since the first character is now a space, it starts at the top of the list. But it still looks hackneyed to me. I am a little flabergasted that shift-tabbing out of a field skips the lost focus logic.

The problem is not with your code, but with the interface to the user. You actually need two fields, the first being a checkbox (with auto complete) with a prompt that says Select All (or something like that) and a second field which is your combo field. If the user un-checks the Select All field then enable the combo box field and visa versa. A much cleaner interface.