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



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

New tab in Tabbed UI is not working the same from a UX as from grid

  • Filter
  • Time
  • Show
Clear All
new posts

  • New tab in Tabbed UI is not working the same from a UX as from grid

    I have been using the tabbed UI with great success for some time. A clients list (grid) had a button that linked to an info sheet which opened in a tab pane. Each new client button selection caused a new tab to open and an employee could keep several client tabs open at the same time. I want to switch to a UX with a list control for the client list with a similar button to open a new tab pane for the selected client. The problem is that, from the UX, unlike the grid, the second selection opens in the "used" pane - the title changes to the new client's name (set in pane title of action JS) but the content does not change (still first client). Note, the target UX is filtered on a session variable (as it was with the grid) and I have checked and it is being set properly. Any suggestions on why I am not getting the same new pane behavior from a UX that I got from a grid?

  • #2
    Re: New tab in Tabbed UI is not working the same from a UX as from grid

    Things to note:

    If you open a GRID from a list, it will work as you want it to.

    If, on your original grid, you change up the search after opening a new tab or two, it will no longer open into new tabs, but start reusing the old ones, the same way.

    When opening a UX in the way you are trying to, you would be better of using an Argument to pass the key value, instead of a session variable.

    I don't know if there is a way to open multiple UX's from a list like you can open multiple grids. I have not tried it.

    One thing is for sure - UX's are very different from Grids. They require an entirely different method of programming. Trying to make them work like grids will only frustrate you.

    You never explained why you are wanting to switch to List/UX from a Grid setup that already works how you want it to. Also, you appear to have posted this in V11, which doesn't have List controls.


    • #3
      Re: New tab in Tabbed UI is not working the same from a UX as from grid

      First, ya I saw that I posted in the wrong forum but did not switch it because I decided to stay with the grid. I note the following:

      Yes, I know that if the target is a grid, there is no problem - just link, whether I am coming from a grid or UX, and the tabbed UI will work great.

      It is the originating element that is the problem. I wanted to switch to a UX with list so that I would have more control over formating. It is used on a tablet mostly and space is a premium. What is frustrating is that the target component - UX - is the same in either version. I would expect the UX to take the session variable no matter where it comes from (it does in a window) and the tabbed UI should work.

      You are also correct that trying to get this to work (a UX like a grid) was more trouble than it was worth and the important formatting comes after the "client" tab is opened. While it would be marginally better to have UX with list for the originating component, I decided to stick with grid for origination. I did not have the option of not using the tabbed UI because of how important is for my employees to have several clients open at the same time.

      While I have always used arguments on target components that take their value from session variables, I have not seen directly passing an argument between components without the session variable. Not sure I need that now that I am apparently committed to the grid for origination but I am curious.

      Anyway, thanks for the input, I really appreciate the reply.