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

Removing minimize/maximize buttons for outer shell

Collapse
X
Collapse
 
  • Page of 2
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 template Next
    #16
    Re: Removing minimize/maximize buttons for outer shell

    The only reason I was interested in eliminating the X at the very top right was to have the user exit Alpha only from an exit button on the main menu. And the reason I wanted to control this is simply to record the exit time, date, and user from Alpha. The entry time, date, and user to Alpha is already posted to a user log via autoexec.

    I no longer care about disabling the outermost X because I am achieving the objective of posting the user, date, and time to the user log by just loading, with the autoexec, on_application_exit(posting code). Sometimes the answer is so obvious that you miss it.

    Thanks to all who contributed their assistance.

    Jeff

    Comment

      #17
      Re: Removing minimize/maximize buttons for outer shell

      Sounds like using autoexec script at startup and the CanDatabaseClose script at the end....

      The on_application_exit(posting code) looks like a function found in prior versions that gives some control but not as much as the 2 newer scripts CanDatabaseClose & OnDatabaseClose do...

      Remember they are scripts not functions and they are called by Alpha at the appropriate times..

      I use this to assign a unique id to the login user and write a record in autoexec and then update that record at the CanDatabaseClose.

      databaseproperties.JPG
      Al Buchholz
      Bookwood Systems, LTD
      Weekly QReportBuilder Webinars Thursday 1 pm CST

      Occam's Razor - KISS
      Normalize till it hurts - De-normalize till it works.
      Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
      When we triage a problem it is much easier to read sample systems than to read a mind.
      "Make it as simple as possible, but not simpler."
      Albert Einstein

      http://www.iadn.com/images/media/iadn_member.png

      Comment

        #18
        Re: Removing minimize/maximize buttons for outer shell

        Originally posted by Al Buchholz View Post
        Sounds like using autoexec script at startup and the CanDatabaseClose script at the end....

        The on_application_exit(posting code) looks like a function found in prior versions that gives some control but not as much as the 2 newer scripts CanDatabaseClose & OnDatabaseClose do...

        Remember they are scripts not functions and they are called by Alpha at the appropriate times..

        I use this to assign a unique id to the login user and write a record in autoexec and then update that record at the CanDatabaseClose.

        [ATTACH=CONFIG]35394[/ATTACH]
        I started out trying to use the OnDatabaseClose with the cancel(), but I couldn't figure out how to override it so I could close through the main menu button. Do you know how?

        What are the downsides of on_application_exit?

        Jeff

        Comment

          #19
          Re: Removing minimize/maximize buttons for outer shell

          Originally posted by Jeff Fried View Post
          I started out trying to use the OnDatabaseClose with the cancel(), but I couldn't figure out how to override it so I could close through the main menu button. Do you know how?

          What are the downsides of on_application_exit?

          Jeff
          1. the cancel() only works in a Can event. The On event is after the event so it can't be stopped - at least not in the way you want to.

          2. Put the code that you are using in the on_application_exit() into the Can or On DatabaseClose and forget about the button on the form...

          3. As stated in my last post, the 2 events Can/On offer more control in their timing. I'd guess that the on_application_exit() is run in the same timing as the OnDatabaseClose script.
          Al Buchholz
          Bookwood Systems, LTD
          Weekly QReportBuilder Webinars Thursday 1 pm CST

          Occam's Razor - KISS
          Normalize till it hurts - De-normalize till it works.
          Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
          When we triage a problem it is much easier to read sample systems than to read a mind.
          "Make it as simple as possible, but not simpler."
          Albert Einstein

          http://www.iadn.com/images/media/iadn_member.png

          Comment

            #20
            Re: Removing minimize/maximize buttons for outer shell

            Originally posted by Al Buchholz View Post
            1. the cancel() only works in a Can event. The On event is after the event so it can't be stopped - at least not in the way you want to.

            2. Put the code that you are using in the on_application_exit() into the Can or On DatabaseClose and forget about the button on the form...

            3. As stated in my last post, the 2 events Can/On offer more control in their timing. I'd guess that the on_application_exit() is run in the same timing as the OnDatabaseClose script.
            I meant to say CanDatabaseClose, not OnDatabaseClose. I used CanDatabaseClose with cancel(), which prevented closing Alpha from everywhere, as it should. I would have been happy to use that, but I couldn't figure out how to override it in the exit button on the main menu. I guess I could have set it up with a conditional variable that was in effect until I changed it in the exit button, but then on_application_exit() has served the purpose in a simple and effective way. I'm still curious to know if you can override the CanDatabaseClose with cancel() (without using a conditional variable) when you get to the main menu button. It's more intellectual curiosity than a need to do it since on_application_exit() is perfectly suited to this situation.

            Jeff

            Comment

              #21
              Re: Removing minimize/maximize buttons for outer shell

              Hi Jeff,
              The CanDatabaseClose script will only exist if you add it, which is the same case for the OnDatabaseclose - just like the Autoexec. If you add the script (s), then you would have to add a condition for the cancel() else you will not be able to override it. I use an Exit button on the toolbar for the main form which sets the Exit_flag to true then logs off and closes the app. The Autoexec dims the variable as global and sets it as false and logs on the user. Thus to disable all the 'X' buttons, you would need to make the CanDatabaseClose cancel() conditional on the same Exit_flag to prevent the app from being closed any other way since that is what disables all the 'X' buttons. How else would get your Exit button to work? Setting the condition IS HOW you override it. ;)
              Robin

              Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

              Comment

                #22
                Re: Removing minimize/maximize buttons for outer shell

                Hi Robin,

                Thanks for your explanation. I suspected that I would need to do as you suggest, setting up a flag to prevent exit until you change the flag in the exit button of the main menu. As it turns out, I disabled all the X exits on forms and only have the remaining X on the highest level (top line) that does not have the same ability to turn off the min/max/close buttons. I was not so interested in preventing the user from clicking on that X and leaving Alpha. Rather, I was more interested in being sure certain procedures take place regardless of how they exit Alpha (such as recording the date, time, and user to a log file). I accomplished this with on_application_exit(). In fact, it is the nature of some users to want to click the red X to leave an application, so it's probably just as well that this is available to them.

                Thanks for your comments.

                Jeff

                Comment

                  #23
                  Re: Removing minimize/maximize buttons for outer shell

                  Sometimes the answer is so obvious that you miss it.
                  That's about where I am at as I reconsider my current routine.

                  With Al's explanation of how to use the CanDatabaseClose script and the on_application_exit() function, I am thinking of using it to log off my app because sometimes my button doesn't get the chance to do it.
                  Robin

                  Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

                  Comment

                  Previous 1 2 template Next
                  Working...
                  X