8 replies to this topic

[Lewis Mccabe]

Hello All,

We have a dynamic button on a paging screen. We cannot force a read of the appropriate record when the button is clicked. For example: the paging screen has 10 lines. The user clicks an order button on the 5th line. No read occurs and the button processes data from the last read. Any thoughts? Thanks.

Lew

Edited by Lewis Mccabe, 26 October 2004 - 07:22 PM.

[Bob Filipiak]

Lew,

Since I do not work in the GUI arena, this answer may be a waste of time, but, I recall that in paging screens, the data from the last read record persists. Found this one out the hard way!!!

So, perhaps you need to "pre-load" the necessary key value on each pass through the screen (i.e. as you display each record). thus when the "on click" event occurs, the read key is "primed". I have found that other GUI environments ( like MS Access) has this kind of behavior.

HTH

Bob Filipiak

[Lewis Mccabe]

Hi Bob,

Since your's is the only reply, I may have to go down your road. It makes sense but I was hoping there was a good alternative. Is there no one out there who has used paging buttons and has solved this problem?

Lew

[John Cummins]

Lou,

We do this by forcing a read of the record. So you have a column in the paging screen that is called "Select" and the user clicks this column before clicking your dynamic button. This field is not a display only, so when they click the column it is after the last read field so it reads the record.

Sometimes instead of having a column called select we simply make make one of the paging field screens serve this purpose, for example a description field. The user clicks on it and it is highlighted then they click the dynamic button. To avoid confusion for the user concerning which field is active we often put a field on top of the paging screen called "Active Patient" or something similar. This field is part of the paging screen using the absolute line number. This is useful when they first enter the screen because the active field as you noted is the last displayed field.

Hope this helps

John

[Lewis Mccabe]

Thanks John,

We'll give it try.

Lew

[Rory]

Has anyone since come across a nicer solution for buttons in a paging screen...?

Rory

[Joseph Bove]

Rory,

There's another, albeit imperfect solution.

You can set @SPSEQ = 1 in the entry logic of the paging screen. The will basically force you into the first record.

There are two thing to remember.

1) You must turn @SPSEQ off (@SPSEQ = 0) when done... the sooner the better!
2) If you use clickable columns, the @SPSEQ = 1 will not be in effect after the user clicks on one of the columns.

The later is probably a ProIV issue that we've not yet reported. I wanted to double check the documentation first.

hth,

Joseph

[Lewis Mccabe]

We did come across a very good solution but a P4 bug prevents use in expanded and contracted modes in same paging cycle. We use static buttons from the parent cycle - 1 for each paging line. You can control them nicely, they only require 1 click and work like a charm. You have to disable unused buttons when you encounter end of file. The expand/contract issue has been reported to PRO-IV. Essentially, when in expand mode, the contracted buttons are not rendered totally invisible and are partially displayed even when both disabled and invisible. No way around it. If not using expand, works great.

Just for reference: Version with bug is 5.5 rev 518 / Client 5.6.7.0
We don't know if problem is with client or server at this point.


Lew

Edited by Lewis Mccabe, 12 February 2006 - 03:37 AM.

[Rory]

Joseph & Lewis,

Thanks for your replies.
We decided to put a global_lscall in the Logic Before of one of the paging display fields (which is underlined to show more detail is available), works well.

Regards
Rory