How to make a MultiPart StatusLine? (OpenInsight Specific)
At 10 FEB 2000 08:04:49PM rayc@symmetryinfo.com wrote:
I did some research on STATUSLINE and found this article.
The STATUSLINE displayed in the above example is broken into 3 parts. How is this done? Or is this multiple STATUSLINE? Can you have more than one STATUSLINE in a form?
Thanks
rayc@symmetryinfo.com onmouseover=window.status=imagine … ;return(true)"
Ray Chan ~ Symmetry Info
At 10 FEB 2000 09:40PM Don Bakke wrote:
Ray,
No, there is only one true STATUSLINE at any one time for a particular window. By "true" I mean a control where default system information and text from a Send_Info command will automatically display in the designated control. The other two so-called statuslines are just regular editline controls that are programmatically handled in the normal way.
dbakke@srpcs.com
At 11 FEB 2000 05:30AM Oystein Reigem wrote:
What about the following:
- Make e.g 3 new edit lines (S1, S2, S3) to display status line info the desired way
- Make the real status line control (S) invisible
- Make a CHANGED handler for S that redistributes the status line info to S1, S2 and S3. E.g if S gets the string "Test§22§3" it could pick out the values "Test", "22" and "3" and display them in S1, S2 and S3. (I've used a normal character as a delimiter here since I doubt system delimiters will work.)
- Oystein -
At 11 FEB 2000 10:17AM Don Bakke wrote:
Oystein,
That sounds like a slick approach except for situations where one statusline needs to be updated at different intervals than the others. For instance, a statusline with date/time information will probably be updated constantly using a TIMER event. Therefore this encapsulated routine will either need to check the existing contents of the other statuslines first (so it can re-post them) or a special provision needs to be written in the logic - for example, if a null is passed as one of the field values the program won't reset the statusline associated to it.
dbakke@srpcs.com
At 11 FEB 2000 10:46AM rayc@symmetryinfo.com wrote:
Don,
]No, there is only one true STATUSLINE at any one time for a particular window. By "true" I mean a control where default system information and text from a Send_Info command will automatically display in the designated control.The other two so-called statuslines are just regular editline controls that are programmatically handled in the normal way.Symmetry Info[/url]
Ray Chan ~ Symmetry Info
At 11 FEB 2000 10:56AM rayc@symmetryinfo.com wrote:
Oystein,
That's a very neat way of doing it. Before I got your response, I played with using an EditTable (w/one row showing) because it automatically displays the gridline (disable heading, row #), I was able to stuff values into the appropriate cell position programatically (not using the Send_Info).
But making the STATUSLINE invisible with a Change Event hook is a good idea. Also, is there an advantage to using 3 Editlines vs an EditTable with 3 (or whatever) columns.
rayc@symmetryinfo.com onmouseover=window.status=imagine … ;return(true)"
Ray Chan ~ Symmetry Info
At 11 FEB 2000 11:00AM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:
To get the 3D look it is easiest just to make a group box wider than the screen so that the horizontal lines are above and below the edit lines.
The multi-box status lines in RevSoft tools are created by using C++ to write the tools!
World Leaders in all things RevSoft
At 11 FEB 2000 12:09PM Matt Sorrell wrote:
Don,
That shouldn't be too difficult to get around. We have a system with an interface wherein updates can be issued to rows. If no information is in the file for a particular field, the system doesn't touch the data. However, if the data for a field is set to a tilde (~), then the system knows to delete the value.
That would be a fairly straightforward extension to Oystein's idea. Always make sure that you send all of the delimiters, and if there is no value don't update that status line. If you want to clear that status line then send a tilde or some other predefined character.
Matt Sorrell
msorrel@greyhound.com
At 11 FEB 2000 12:12PM Oystein Reigem wrote:
Don,
The problem occurred to me already, but I didn't want to clutter things up.
To distinguish between the two cases "clear" and "keep the old value" one of them could be represented by "" and the other one by some special code. Making that code unique isn't too difficult. One could e.g prefix each value with a character (another code) telling if the following string is a value or a code.
Another possible problem is the delimiter conflicting with the characters of the values, but that can be solved too.
- Oystein -
At 11 FEB 2000 12:17PM Oystein Reigem wrote:
Ray,
I cannot really think of any objections to using a "stripped" one-line edit table, except the looks. You can space edit fields apart, but you might not want that.
(Actually there's a slight advantage with the edit table in that you save a couple of controls and don't hit the max limit so easily. (There's a limit to the number of controls in a form, if you don't know already.))
- Oystein -