Jim,
Forgot to mention in the approach I outlined above you do not have to worry about not clearing the screen in the calling function's LS1, because the global is called in the entry logic of the calling function. So it gets called and stays there as long as none of the formats in the calling function overwrite it.
hth
John
- ProIV Resource Centre
- → Viewing Profile: Posts: John Cummins
Community Stats
- Group Members
- Active Posts 10
- Profile Views 4,179
- Member Title Member
- Age Age Unknown
- Birthday Birthday Unknown
-
Gender
Male
-
Location
Ramsey , United States
Previous Fields
-
First Name
John
-
Surname
Cummins
-
Nationality
us
-
Year Started ProIV
1987
-
Highest ProIV Version Used
4.6
0
Neutral
User Tools
Friends
John Cummins hasn't added any friends yet.
Latest Visitors
No latest visitors to show
Posts I've Made
In Topic: Icon scope
17 October 2006 - 04:08 PM
In Topic: Icon scope
17 October 2006 - 03:58 PM
Jim,
We have been using the same approach for over a year without problem. In our setup each function calls a global screen(header function) in the calling function's entry logic which paints the screen with header information with anywhere from 3 to 6 icons (the icon presentation is set based on parameters passed to the global by the calling function).
As you note the calling function adopts the fnkey logic from the header function so this logic must be set in each function, and we simply solved this by dedicating some fnkeys at the end of each function.
It has worked well for us.
John
We have been using the same approach for over a year without problem. In our setup each function calls a global screen(header function) in the calling function's entry logic which paints the screen with header information with anywhere from 3 to 6 icons (the icon presentation is set based on parameters passed to the global by the calling function).
As you note the calling function adopts the fnkey logic from the header function so this logic must be set in each function, and we simply solved this by dedicating some fnkeys at the end of each function.
It has worked well for us.
John
In Topic: The passing of Curtis Goodrich
29 March 2006 - 08:14 PM
Glenn,
This is certainly sad news. Curtis was not only a very good guy but a great help in the early days of Proiv. He was always fun to be with and had a great sense of humor.
John
This is certainly sad news. Curtis was not only a very good guy but a great help in the early days of Proiv. He was always fun to be with and had a great sense of humor.
John
In Topic: Button on paging screen
28 October 2004 - 12:48 PM
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
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
In Topic: More changes at PROIV Inc.
04 April 2001 - 12:12 PM
Rob,
Your approach is the correct one. Leave things as they are. People participate in the forum for their own benefit and that of other particpants, and can weed out any useless chatter.
John
Your approach is the correct one. Leave things as they are. People participate in the forum for their own benefit and that of other particpants, and can weed out any useless chatter.
John
- ProIV Resource Centre
- → Viewing Profile: Posts: John Cummins
- Privacy Policy