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

CSS syntax for wherever a component is opened

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

  • CSS syntax for wherever a component is opened

    I want to affect an element of an AA component via local CSS. e.g.

    #GRID1_ROWSPERPAGE_BOTTOM {
    width:75px;
    }

    This works fine when the grid opens directly. However, AA renames the component ID when it is opened from a parent control, which happens often. The id becomes "GRID1_IDP_CLIENT_EVPC_IDP_CLIENTS_221445LJLE_ROWSPERPAGE_BOTTOM" for example. FYI it only has the universal class of "iOSEdit."

    I know I need to use wildcards for an effect like "#*ROWSPERPAGE_BOTTOM" but I've searched and I can not figure out how the syntax works. Anybody know this one?
    Last edited by ecalan; 03-18-2018, 11:33 PM.

  • #2
    Re: CSS syntax for wherever a component is opened

    You don't say how you're opening your child grid... or from where... but... usually there is "Grid alias" property you can fill in. For example, using the Action "Open a Grid component" I opened a Grid from a UX Component. I changed the "Grid alias" from <DefaultAlias> to TRAININGDATES.

    The ID you're after on the opened grid is now... TRAININGDATES_ROWSPERPAGE_BOTTOM

    There is a bit of help for the Alias property. Click on the ? beside the Alias input field to see if it's of any help to you.

    Comment


    • #3
      Re: CSS syntax for wherever a component is opened

      David, Thanks, I did not know an alias created the ID prefix for elements. That will definitely come in handy but I still wanted to figure out the css wildcard syntax so I can set the CSS once on the main page and have it apply to all components. So, when a grid is reused for a lot of children, e.g. filtered, new, custom view, etc., I did not want to have to make any changes repetitively. I did find the syntax - I would say finally but it seemed to come up first this time when I searched. Hmmm. Here it is if anyone else comes across this problem.

      *[id*='ROWSPERPAGE_BOTTOM'] {
      width:75px;
      }

      Comment


      • #4
        Re: CSS syntax for wherever a component is opened

        Good sleuthing. Image that working in Alpha... I've never used it. Where did you find it?

        Comment


        • #5
          Re: CSS syntax for wherever a component is opened

          Thanks David, sleuthing is half the fun. Not sure where I eventually got it from but it was the combination of a couple of posts in different web development forums. It took me years to realize that Alpha takes all CSS. If you can find the ID or Class the server assigns to an element with webmaster tools (old firebug), you can hack it with standard CSS in the local CSS properties. I put 3 lines of CSS in the tabbedUI (Yes, I think it is indispensable) and all grids in my app will have the "correct" row selector. Happy days indeed.

          Comment

          Working...
          X