Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 06 JUN 1998 11:49:31AM DSig (SigSolutions) wrote:

On all my fields I have a Got/Lost focus process which changes colors of the fields to show which field has focus.

If a user saves the record before all 'required' fields have been filled the system sends the 'data required …' and sets the cursor on the field missing data.

The odd thing is that the GOTFOCUS event does not fire. In some cases the GOTFOCUS event also performs other functions (auto popup, calculation of data etc) so it is very important that the GOTFOCUS fires.

dsig

David Tod Sigafoos ~ SigSOlutions

[email protected] cis:70302,77 voice:503-639-8080


At 06 JUN 1998 04:41PM Don Bakke wrote:

Dsig,

Sounds like the Required Fields logic uses Set_Property(@Window.control, "FOCUS", Yes$) rather than Set_Property("SYSTEM", "FOCUS", @Window.control), which avoids triggering the event. I'm not sure how to get around it.

[email protected]

SRP Computer Solutions


At 08 JUN 1998 08:16AM Jeff Word wrote:

Is that the main differnce between the two methods of focusing? (That the gotfocus event does not get fired) Are there other differences? I have been using this approach "Set_Property(@Window.control, "FOCUS", Yes$)" and sometimes I had to do a gotfocus manually. If I change them to "Set_Property("SYSTEM", "FOCUS", @Window.control)" then I should not do a manual gotfocus, correct?


At 08 JUN 1998 10:49AM Don Bakke wrote:

AFAIK the only difference (at least that matters) is the GOTFOCUS event being fired. You should not need to do a manual gotfocus.

[email protected]

SRP Computer Solutions


At 08 JUN 1998 03:19PM Gene Gleyzer Revelation wrote:

David,

Don is correct: the Form IO logic intentionally uses

 set_property (ctlId, FOCUS$, TRUE$)

which prevents generation of the GOTFOCUS event. The general approach is that "error hanling" doesn't generate the same events that the user navigation through the form does. In your case the GOTFOCUS event is not generated, but instead the SYSMSG event is:

 send_event ("SYSMSG", SYSMSG_REQUIREERR$)

However, this doesn't tell you what control is required to be filled in, so you would have to post_event from the SYSMSG event to allow the focus to be set by the system. In the handler for the posted event (like OMNIEVENT) you can get the current focus and send it a GOTFOCUS.

I put the request into our SPR system to provide "SYSMSG" event with more info for SYSMSG_REQUIREERR$ case – it will be done for the next release.

Thanks you

Gene


At 08 JUN 1998 08:31PM Dsig (SigSolutions) wrote:

Gene,

Thanks for the response ..

I am not sure if you plan to update the sysmsg to tell about the control OR if you plan to force the system focus.

For example if you have a popup which the user must select from (displays on gotfocus if not data in current control) then if the user tries to save you would think that you want to force the gotfocus event .. yes?

Thanks again for the quick follow up .. look forward to the fix

dsig

David Tod Sigafoos ~ SigSOlutions

[email protected] cis:70302,77 voice:503-639-8080


At 09 JUN 1998 09:04AM Gene Gleyzer wrote:

David,

I plan to add an extra parameter to SYSMSG in the situation you have described – re-positioning focus as a result of "required field" processing.

I'm not quite sure what exactly your second question is, but I believe that you can implement this functionality by overriding/supplementing SYSMSG event (having the "required field" as a parameter gives you all the information you need)

gene


At 09 JUN 1998 10:38AM DSig (SigSolutions) wrote:

]I'm not quite sure what exactly your second question is, but I believe that you can implement this functionality by overriding/supplementing SYSMSG event (having the "required field" as a parameter gives you all the information you need)

I guess I am in my 'confuse them state'.

To me it seems pretty simple.

1) a person buys OI

2) they create a form with edit lines

3) one of the edit lines they wish to force the user to select data from a popup (not a dropdown or any other list box but a popup

4) on the gotfocus event they check to see if there is data in control and if not then display popup for selection

5) check required so that the user can not exit the control without entering data

At this point the developer should be pretty sure that the bases are covered. The SAVE should check for data in the required control. If no data then give message and put focus back on control (thus forcing the popup etc etc etc).

Now being an old rti person (user of products) I realize that there is some wizard like hack to make it work .. check a, toggle a couple of bits, calculate the changes of the moon and the multiply by sidereal time .. I had just hoped that these things would have been done by the developers of the tool.

Thanks for the reply

dsig

David Tod Sigafoos ~ SigSOlutions

[email protected] cis:70302,77 voice:503-639-8080

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/a5e3281167a387a38525661b0056ee62.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1