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

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

Hide the control panel

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Hide the control panel

    I put this here for those that do not want their users to see the control panel. That rascal always shows up these days unless you get a little creative. I thought I would post my solution for anyone that could use it. With this, I can also open or close the control panel for myself but the user never sees it.

    'STEPS - Note that everything here is commented. Remove the ' where appropriate

    '1. Set a global variable to indicate hidden or not. (I call mine hide182 )
    '2. Set a global variable to true if you are running on your machine. (I call mine mymachine )
    '3. Put controlpanel.hide() as an on init in your startup form ( I call mine BHS_Manager )
    '4. Create a blank screen and add the following as an on init ( I call mine cleanscreen )
    ' 'Close current form or browse window.
    ' parentform.close(.f.)

    ' Open a Form or Browse layout

    ' DIM Shared varP_BHS_Manager as P
    ' DIM layout_name as c
    ' layout_name = "BHS_Manager"
    ' DIM tempP as p

    ' tempP=obj(":"+object_Name_normalize(word(layout_name,1,"@")))
    ' Test if pointer is valid
    ' if is_object(tempP) then
    ' Test if pointer refers to a form or browse
    ' if tempP.class() = "form" .or. tempP.class() = "browse" then
    ' If so, then activate the already open window
    ' tempP.activate()

    ' else
    'Window is not already open, so open it
    ' varP_BHS_Manager = :Form.view(layout_name)


    ' end if
    ' else
    ' varP_BHS_Manager = :Form.view(layout_name)


    ' end if

    '5. Instead of opening your initial screen from your autoexec, open your cleanscreen.
    ' This is necessary because even if you have a controlpanel.hide() as an on init
    ' behind your initial screen, the control panel shows up unless you go somewhere else first.
    ' Add the following as an on init for your first form

    ' 'Hide the Control Panel and set the variable
    ' controlpanel.hide()
    ' var->hide182 = .t.

    ' if var->mymachine = .f.
    ' button2.hide()
    ' hide182.hide()
    ' end if


    '6. Put the following code behind a button on the form you would
    ' like to open the control panel from. This hides or shows it based on
    ' the value of hide182

    ' if var->hide182 = .t.
    ' :controlpanel.show()
    ' var->hide182 = .f.
    ' goto done
    ' end if
    ' if var->hide182 = .f.
    ' :controlpanel.hide()
    ' var->hide182 = .t.
    ' end if
    ' done:

    '7. Be sure to hide the button and hide182 if you are not running from your own machine
    ' For this I have the following code as an on init on the form I open/close the control panel from.

    ' 'Hide the Control Panel and set the variable
    ' controlpanel.hide()
    ' var->hide182 = .t.

    ' if var->mymachine = .f.
    ' button2.hide()
    ' hide182.hide()
    ' end if

    I hope this helps those that endeavor not to confuse their users with what you don't want them to see.



  • #2
    Gene, nice bit of processing.
    Looks a little complicated to a simpleton like me.

    The quick and dirty way I do it is;
    In Workspace properties, set CP to HIDE. You will get a warning.
    On, say a menu form, create a simple button bottom right with "Copyright Gene" or similar and make it password protected with the show CP code behind it.
    I often use an innocuous logo as the button.
    You can also use a HotSpot which is invisible unless you know it's there.
    See our Hybrid Option here;
    https://hybridapps.example-software.com/

    Comment


    • #3
      Thanks Ted,

      One unmentioned benefit of the open a useless form first approach is the current screen sizing issue is greatly minimized in its affect. The first screen that appears can size too small to be functional at this time. I don't care if the cleanscreen shows too small. No one sees it anyway and when the first screen I want is opened second, I don't see a sizing issue. That sizing issue is what led me to be so creative.

      Comment


      • #4
        Now I understand the logic.
        See our Hybrid Option here;
        https://hybridapps.example-software.com/

        Comment

        Working...
        X