In a number our screens we skip around fields depending on data and system setup. Under green screen the fields didn't show anything when we fld skipped over them.
Does anyone know how to stop the edit box from showing on a screen (under GUI) for fields you want to skip and not allow entry? The display only ones don't show up and you can't click to them, but it makes the screen look very un-professional when you have the edit boxes showing with no headers.
Don
Click the link below to see the new game I'm developing!
2 replies to this topic
#2
Chris Pepper
-
- Members
-
- 369 posts
ProIV Guru
- Gender:Male
- Location:United Kingdom
Posted 13 April 2000 - 10:58 PM
I'm not currently using GUI but the approved method is to set the field as '' (ie an empty constant) not $DUMMY or a scratch field and set a zero start line & column and length. This means it shouldn't be shown with a box in GUI.
#3
Guest_Anonymous_*
Guest_Anonymous_*
-
- Guests
Posted 22 April 2000 - 08:05 AM
I presume you are not referring to 'dummy' fields, but actual input fields that you want to skip under certain conditions?
Jumping fields (and not displaying the white space) in GUI is not easy. As soon as you enter a PRO IV screen characteristic in GUI, all input fields are drawn. They are not rendered as you reach each one.
One way around this (and I have used this in the past) is to put the fields in their own characteristics, i.e, set up an overall controlling characteristic that encompasses all fields, but then within that define separate characteristics for each block of fields that you might want to skip. Make sure that your first nested characterstic contains fields that you always want displayed. Also make sure that there is a 'dummy' fields between each nested characteristic (that sits in the very outer char.) so that you can control a field jump over the next one if required. This approach obviously makes any screen navigation (i.e. cursoring back to a field in a previous characteristic) impossible, although if you are developing in GUI, then putting an edit button at the bottom of the screen to allow the user to jump back to the relevant place would probably be a better solution any way.
Jumping fields (and not displaying the white space) in GUI is not easy. As soon as you enter a PRO IV screen characteristic in GUI, all input fields are drawn. They are not rendered as you reach each one.
One way around this (and I have used this in the past) is to put the fields in their own characteristics, i.e, set up an overall controlling characteristic that encompasses all fields, but then within that define separate characteristics for each block of fields that you might want to skip. Make sure that your first nested characterstic contains fields that you always want displayed. Also make sure that there is a 'dummy' fields between each nested characteristic (that sits in the very outer char.) so that you can control a field jump over the next one if required. This approach obviously makes any screen navigation (i.e. cursoring back to a field in a previous characteristic) impossible, although if you are developing in GUI, then putting an edit button at the bottom of the screen to allow the user to jump back to the relevant place would probably be a better solution any way.
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
Click the link below to see the new game I'm developing!
