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

Help-- Filtering List in UX

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

    Help-- Filtering List in UX

    All: I am new to Alpha Anywhere and while I love the power of the tool, I have to admit that I'm getting very frustrated with it! This week alone, I have been through roughly 480 threads on the forum and watched many videos, but I still cannot find how to do something with initializing list component on a UX. I realize that this is probably very easy to do, but I am struggling here.

    I am building a library look-up mobile application which contains two panels: the first contains search criteria (search value, search type, item class, and item type and a search button) and the second panel contains the search results which is only displayed once the end-user enters search criteria clicks the search button on the first panel. The "search" button works well with all of the search criteria being correctly processed and returning the correct records on the search results panel.

    Unfortunately, my problem is that the list obtains all records in SQL statement (which is not filtered) when the UX is initially rendered (and with over 100K records, it is taking a while for the UX to display). It doesn't make sense to have the SQL statement execute until the end-user enters search criteria and clicks the search button.

    Everything that I've read pertaining to the list control starts out with a pre-populated list which is then furthered filtered based on end-user provided search critiera. Can anyone please provide direction to this me on how to make the list behave dormant until the end-user clicks the "search" button in the UX?

    Any assistance you can provide to me is greatly appreciated!

    #2
    Re: Help-- Filtering List in UX

    Hi David,

    Welcome.

    There is a lot of stuff in Alpha Anywhere... and what you're looking for is most likely not far from reach. So keep asking.

    Your List control contains 2 properties that will be helpful in this case. These are found in the List Properties Tab of the List control.

    Delay render till visible
    Delay render till explicit refresh

    You're probably going to need Delay render till visibile.

    The List will not be rendered until the panel card it's in is brought into view. Then it will fire.

    Comment


      #3
      Re: Help-- Filtering List in UX

      Originally posted by Davidk View Post
      Hi David,

      Welcome.

      There is a lot of stuff in Alpha Anywhere... and what you're looking for is most likely not far from reach. So keep asking.

      Your List control contains 2 properties that will be helpful in this case. These are found in the List Properties Tab of the List control.

      Delay render till visible
      Delay render till explicit refresh

      You're probably going to need Delay render till visibile.

      The List will not be rendered until the panel card it's in is brought into view. Then it will fire.
      David: THANK YOU for the quick response and for pointing me in the right direction with the list properties. The "Delay render till explicit refresh" property is exactly what I needed to delay the SQL from triggering until the end-user entered the search criteria! It works beautifully now. I'll be glad when I'm more up to speed with Alpha Anywhere. Thanks again for your assistance.

      Comment

      Working...
      X