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

Refresh Panel Card?

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • GGandhi
    replied
    Re: Refresh Panel Card?

    The session variable is changed using code. Even though the session variable has changed, the button enable/disabled state remains the same
    since session is in the server, the ux/dialog that resides in the browser does not know that the value has changed unless a call is made to the server. what ever the code that is changing the session variable may be used to change some value here in the ux/dialog. if that is possible in your situation then the ux will reflect that change in the buttons.

    Leave a comment:

  • Davidk
    replied
    Re: Refresh Panel Card?

    I prefer using State Variables over Session Variables. Session Variables are a bit too finicky to work with for me. I never get the feeling that they're persisted all the time, and you kinda have to jump through a couple of hoops to get them right or reflect their true values. State variables are easily accessible. If I'm working with one or more embedded components to which I need to pass data through their arguments setup, then the main component (which may use session vars, if I'm forced) will establish what Frank suggests... controls which hold those session values. Then I pass along argument data based on those controls and never bother with the session vars again.

    However, if you really want to continue with session vars in the manner you're using them... then you need to refresh the client-side stuff. You can return this from the XBasic code that resets your session var and it will refresh the enable expression on your button.

    Code:
    yourXBasicFunction = "{dialog.Object}.refreshClientSideComputations();"
    But beware... this will refresh everything that is show/hide, enable/disable, etc.

    Leave a comment:

  • frankbicknell
    replied
    Re: Refresh Panel Card?

    It would be better to enable / disable client side.
    One way is in the callback have it set a dummy field value, for example an unbound numeric field set to 0 or 1, then have to buttons enable property look at that field.
    ex,
    An unbound hidden (client side) field called ButtonEnableState. In your buttons client side enable property have 'ButtonEnableState = 1'.
    You can set the default value of the hidden unbound field to 0 - Button is Disabled or 1 - Button is Enabled.

    Otherwise you would probably have to use a javascript function to do a callback to get the new value then set the buttons enable state. That is a lot of work to change the buttons enable state.

    Leave a comment:

  • Ronald Anusiewicz
    started a topic Refresh Panel Card?

    Refresh Panel Card?

    I have a button whose enable/disable property is controlled by a session variable. The button is in a panel card. The session variable is changed using code. Even though the session variable has changed, the button enable/disabled state remains the same. The only way I can make the button refresh is to reload the page.

    How do I force the button's panel card to refresh/update/reload?

    I've tried watching videos and searched the message board and I can't figure this out.

    Thanks,

    Ron
    Tags: None
Previous template Next
Working...
X