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

Show/hide expressions being overwritten by Alpha

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

    Show/hide expressions being overwritten by Alpha

    On a dialog I have a button that has the client side show/hide property set to 0 (I also tried using 1=2). The dialog that is behaving this way is a popup window that simply displays a 'working' message and has the previously mentioned hidden button. The buttons functionality is that its onClick event closes the dialog. The 'working' dialog is initiated from a button click using action javascript on another dialog which will use action javascript to open the 'working message' dialog. Following in the action javascript is some inline-javascript that simply does a submit. Everything works fine at first, but after doing a couple of saves, the button becomes visible. The window is closed on the server-side 'afterDialogValdiate' event. The window is closed by clicking the hidden button by appending the e.javascript in the 'afterDialogValidate' event after the save is done. Everything is always saving properly. Everything functions as it should when the button is hidden, but not when its visible. The show/hide is never altered anywhere in the code. Basically, why would Alpha force the button to be visible if the client side show hide is always false? I have been messing with this for a few days and I can't figure out why this is happening. Has anybody else ever had this problem? If so, how did you fix it? From what I have narrowed down, it seems to be coming from something with when a save/submit is performed. Any help or advice would be greatly appreciated.

    Thanks,
    Dustin

    #2
    Re: Show/hide expressions being overwritten by Alpha

    You may want to break your question into multiple pieces.
    Who wants to read a book? :P

    Basically, why would Alpha force the button to be visible if the client side show hide is always false? (maybe there is a server side re render and the client side expression doesnt fire again? Maybe messing with the e.javascript messed up alphas recalculations?)

    'The window is closed by clicking the hidden button by appending the e.javascript in the 'afterDialogValidate' event after the save is done.' - If all you wanna do is close the window, why not handle the dialogs event and output some e.javascript to close the window yourself? This would alleviate the need for a hidden button.
    Scott Moniz - Computer Programmer/Analyst
    REA Inc.
    http://reainc.net
    (416)-533-3777
    [email protected]

    REA INC offers consulting services, programming services, systems design, database design, third party payment gateway integration (CHASE, PAYPAL, AUTHORIZE.NET) and developer support.
    If you need custom code, or 1-to-1 mentoring in any facet of your database/web application design,
    contact us to discuss options.

    Comment


      #3
      Re: Show/hide expressions being overwritten by Alpha

      Thanks! Sorry about the long question, I just always see the opposite on here with people not giving enough information. I will definitely look into these suggestions and see if it solves my problem. Once again, thank you very much for taking time to answer my question.

      Comment


        #4
        Re: Show/hide expressions being overwritten by Alpha

        Not a problem. Lots of information is GOOD. But the way it is presented is hard to follow (Think about spacing between paragraphs in a newspaper)

        Something just may not be reloading the calculated fields, You do have the option to move your code to server side.
        If the button is just closing the window Click your button and click the 'View Javascript' (Next to the View Javascript).
        Take that javascript and append it to e.javascript in the afterDialogValidate.

        Button circumvented, Problem fixed.

        Gluck!
        Scott Moniz - Computer Programmer/Analyst
        REA Inc.
        http://reainc.net
        (416)-533-3777
        [email protected]

        REA INC offers consulting services, programming services, systems design, database design, third party payment gateway integration (CHASE, PAYPAL, AUTHORIZE.NET) and developer support.
        If you need custom code, or 1-to-1 mentoring in any facet of your database/web application design,
        contact us to discuss options.

        Comment


          #5
          Re: Show/hide expressions being overwritten by Alpha

          Run it in Live Preview in Firefox or Chrome and find out if there are any Javascript errors occurring at any point. Sometimes a Javascript error elsewhere on the page causes the Javascript being used in show/hide expressions to fail regardless of what the expression is. That said, I use 1=2 throughout our application.

          Comment


            #6
            Re: Show/hide expressions being overwritten by Alpha

            Thank you everybody for the help! The problem has been resolved. It was due to using cached dialogs. This issue was happening in a large application and we were able to figure out that caching was what was causing the issue. Once the 'use cached dialog' option was changed, everything worked fine.

            Comment

            Working...
            X