Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook
Devcon 2020 Goes Virtual! LEARN MORE >

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

window jumping question

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    window jumping question

    I know you can use ui_freeze to "freeze" the screen using the current form... but is there a way to freeze the screen while you are switching forms?

    All that jumping is rather annoying.
    Tags: None
    #2
    RE: window jumping question

    Jeff,

    One of the advances that will show up with A5V5 is better screen handling. A5V.* was limited by the way in which Windows loaded menus and toolbars, which resulted in screen jump. This was particularly annoying if some forms have menus and toolbars and some do not. Attached is a short quote from the Release Notes for the A5V5 beta.

    A5V5 has so many new features that it is almost mind boggling. The really neat part is that with all of the genies available, these new features are easier than ever to use.

    One way to reduce the "jump" in current versions is to have a toolbar on every form, even if it is blank. In this way, every screen is the same size and the problem isn't as noticeable.

    Jerry

    Comment

      #3
      RE: window jumping question

      I had read that...before we purchased 4.5... but their idea of "isn't as noticeable" and mine are not the same... very much noticeable when switching forms...

      All my forms and windows are set to the same size and they all have 1 toolbar... so I guess I have done all I can do for that.. no biggie.

      On a different note.... I am attempting my first actual Xbasic script.. at least one that I couldn't steal from somewhere else :)

      Simple password checking script and I wonder if you could take a look at what I have so far and let me know if I am on the right track. It's not done or even tried yet but it would be helpful to nip any problems in the bud early.
      If ya got time anyway...

      This form (Login) has 2 fields that use 1 layout level variable (user) and a session level variable(pass). Posted here:

      'password = fubar
      dim tbl as p


      'check for a blank username
      '--------------------------
      SELECT
      CASE user=""
      GOTO NOUSER
      END SELECT


      'Open table and set primary index
      '---------------------------------
      tbl=table.open("Users",FILE_RO_SHARED)
      tbl.index_primary_put("username")

      'Locate user's record
      '---------------------
      tbl.fetch_loc_next(user)
      passwrd=tbl.password

      'Compare username & password entered against record
      '---------------------------------------------------
      SELECT
      CASE passwrd pass
      GOTO DENY

      CASE passwrd = pass
      GOTO SUCCESS

      END SELECT

      'Abort script, remove when script is completed & functional
      '------------------------------------------------------------------
      GOTO END

      'Inform user there was no username entered
      '-----------------------------------------
      :NOUSER
      ui_msg_box("No UserName entered, Try Again")
      GOTO END

      'Login successful message
      '-------------------------
      :SUCCESS
      ui_msg_box("Login Accepted")
      GOTO END

      'Login failed message
      '--------------------
      :DENY
      ui_msg_box("Invalid Username/Password: Login Failed")

      :END
      end

      Thanks in advance for your help.. or everyone's help as the case may be.

      Comment

        #4
        RE: window jumping question

        Jeff,
        Attached is a script I originally write in ver 1 which is attached to a "continue" button on a form. There are 2 variables that the user enters and then I check for a valid user-id and passoword against the security table(secure2). I also check to see if someone is logged on as this user and if the password needs to be changed (every 3 months). Thisw script is for ver 5 because I needed the aa.addin variables. they are like "super Global" variables. I have many multiple applications called from theis first menu application and I need to trace the user throughout.

        Hope this helps.

        Tom

        Comment

          #5
          RE: window jumping question

          Jeff

          The best way to learn xbasic is read the manual and experiment. Not a bad first effort. Your logic is good, but there are a couple problems.

          Attached is a text file with your code modified / simplified and a few additions and comments. A couple of issues pop up.

          1. Any table you open must be closed.

          2. Your syntax for ui_msg_box is incomplete. It needs both title and message text.

          3. You need to account for a record not being found on fetch()

          4. And finally, what happens if the logon fails? The attached example gives one way which is rather final, but it will stop an incorrect login.

          Jerry

          Comment

            #6
            RE: window jumping question

            Thank you Jerry...

            I realized shortly after sending the message that I had nothing there to deal with no match on the record search. Had placed a note there and was in the process of researching this... thnx.. saved me some digging...

            And I like what you did with the messaging... reuseing the code.. doh!.. I woulda thought of that... eventually :)
            well ... mebbe

            And the deal about closing a table if you open it... I remember reading that now... and that solves another annoyance that I have been meaning to adress... now I know what to look for to solve that. The documentation I have read once... and Peter Wayne's book is open all the time... sure wish Alpha would have printed the darn thing... It's just not practical to lug around 35 pounds of computer to read a book...lol

            I will make some changes and let ya know how I make out... thanks again.

            Comment

              #7
              RE: window jumping question

              Hmmmm.. tried your script... fails with a "can't locate that symbol"

              it's not the ui code.. I eliminated that... so I made a test script in its place using:

              code = ui_stop_symbol
              ui_msg_box("Stop","You made a mistake",code)

              it displays correctly...

              So whats the "symbol" that it cant find?

              Comment

                #8
                RE: window jumping question

                Dunno,

                Its there - I'm here, and my big S just fell off. Actually, the A5 error messages don't tell you much. I use my own error trapping.

                Put this at the top of the script as the first line

                on error goto error_handler

                At the very bottom of the script cut and paste the following lines. Make sure you include the END statement before error_handler

                END

                error_handler:
                msg = error_text_get(error_code_get())+chr(10)+chr(13)+"Error occured at line "+str(error_line_number_get(),4,0)
                ui_msg_box("Error", this.name()+" - "+msg)


                Now, if your script hits an error, it will give the message and the line number. Makes debugging easier. Also, you can use the Alpha debugger to "walk" through a script. Just put this as the first line in the script.

                debug(1)

                That will turn the debugger on and you can use F12 to run one line at a time.

                Jerry

                Comment

                  #9
                  RE: window jumping question

                  Found the big S and it stands for stupid. Attached is a revised script. I had a goto to a label, but never put the label (message:)in the script. That was the symbol it couldn't find. And neither could I

                  Jerry

                  Comment

                  Previous template Next
                  Working...
                  X