/ Forums / Advansys Formativ / Creating Solutions with Formativ / User Profiles and Scroll bars

  • Creator
    Topic
  • #4262
    sfritz
    Participant

      I am successful in using a formativ applet and writing to an MySQL database but now it is required to include the userid of the person keying the data. Is is possible to obtain the groupwise user’s login information and store it variable, then write that variable out. I am trying to prevent writing a login in screen since the user has already submitted a valid userid/password.

      I have looked thru the forum and could not find where I can enable a vertical scrollbar on my Formativ applet. Can you point me in the write direction?

      Thank you in advance for your help.
      Sfritz

    • Author
      Replies
    • #7652
      lp_irovetz
      Participant

        Hi,

        To know who is log in GW, you need to use Account properties
        In this object you find account.Owner which is the address of you UserID

        For vertical scrool bar, where do you want to put it, in design forms ?

        Regards

        L.P. Irovetz
        Arcane GroupWare

        #7651
        Support 3
        Participant

          If the GroupWise client is running then you can use “groupwise.EnvUserID” token to return the current user ID.

          Regards,
          Advansys Support

          #7649
          sfritz
          Participant

            Thank you both for how to obtain the user information. I will be trying that out and let you know how I make out.

            As for the vertical scroll bars I want them to be available at runtime when a form is launched. The reason is that the resolution I am developing at is not used by all staff. Or is there a way to have formativ dynamically resize according to screen resolution.

            #7650
            Support 1
            Participant

              While editing (designing) a form, you can adjust properties of a form’s horizontal and vertical scrollbars (HorzScrollBar, VertScrollBar) in the Object Inspector. By default, form scrollbars will appear automatically, ie. whenever a control on the form is positioned outside (or overlapping) any edge of the form. Example controls are Label, EditBox and Button.

              However, I would suggest that you avoid designing a form which relies on scrollbars to provide access to ‘out of bounds’ controls. This honours the user interface design guideline of minimizing the number of steps a user must take to achieve something. A useful rule of thumb is to optimize the design for an ‘average’ screen resolution of 1024 x 768, but also to support lower (800 x 600) and higher (1280 x 1024). The form should be tested with each screen resolution.

              One possibility is to allow the user to resize or maximize the form:

                Form1.BorderStyle = bsSizeable

              unless the form is really a (fixed size) dialog box:

                Form1.BorderStyle = bsDialog

              This option can be used effectively in combination with the Align property of each control on the form. If, for example, a form has a number of Label and EditBox controls, all of them could have Align = alTop; then regardless of the form size, all controls align automatically, from top to bottom, to occupy the available horizontal space. Consider using Panel or Bevel controls to provide spacing between other controls.

              Note that you may need to take into account the variation when the Windows display is set to use large (or small) fonts.

              You may find it necessary to separate a user interface into two (or more) forms in order to honour these guidelines.

              More information on the design of forms is available in the help file which documents the Standard and Additional tabs of the Component palette. Search the index for “user interface” then navigate to “Managing layout”.

              I hope this helps.

              Regards,
              Advansys Support

            Viewing 4 replies - 1 through 4 (of 4 total)
            • You must be logged in to reply to this topic.