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

Login Component CSS

  • Filter
  • Time
  • Show
Clear All
new posts

  • Login Component CSS

    Why does the login button on the login component not respond to CSS for ButtonHover and ButtonPressed selectors. I have no problem for the CSS on the Button selector. I also have no problem with the buttons on any of my grids just the login component. Any thoughts would be much appreciated.

  • #2
    Re: Login Component CSS

    I just typed in CSS in the Wiki..

    Alpha Software documentation wiki

    Location : Alphapedia


    Search Advanced search: CSS Date Search:
    Multiple select
    Clear Filter

    Found "CSS" in 0 wiki pages
    No pages matched the search criteria

    CSS of Alpha should be known to everyone so we can all relate to the same base settings.
    Insanity: doing the same thing over and over again and expecting different results.
    Albert Einstein, (attributed)
    US (German-born) physicist (1879 - 1955)


    • #3
      Re: Login Component CSS

      Apparently the WiKi is unfamiliar with CSS.

      Actually if you pause for a second before pressing enter a few selections do appear, but it's still a piece of junk.

      WiKi CSS.gif
      AlphaBase Solutions, LLC

      [email protected]


      • #4
        Re: Login Component CSS

        Originally posted by azz211 View Post
        Why does the login button on the login component not respond to CSS for ButtonHover and ButtonPressed selectors. I have no problem for the CSS on the Button selector. I also have no problem with the buttons on any of my grids just the login component. Any thoughts would be much appreciated.
        The buttons on the login component do not currently support those styles.


        • #5
          Re: Login Component CSS

          Why not and when will it. I think it reasonable to expect to be able to have a login that matched your app.
          Insanity: doing the same thing over and over again and expecting different results.
          Albert Einstein, (attributed)
          US (German-born) physicist (1879 - 1955)


          • #6
            Re: Login Component CSS

            Well - I never even noticed that they didn't, so I guess that tells you something about how much that matters to me. Then again, I'm my own client, so I kinda don't count - because I'm not breathing down my own neck asking "why mommy why..." like a "real" client might.

            About the wiki and searching for CSS - the new Wiki Search Assistant (under Help in your A5 Developer) does find CSS, and finds a lot of other things that searching in the Wiki itself does not. That, and the Video Finder, are now real life savers for me sometimes. I wouldn't touch Search in the wiki itself with a ten foot pole, and fortunately now I don't have to.
            Wendy Welton
            past & future Alphaholic - deliberately falling off the wagon!



            • #7
              Re: Login Component CSS

              When using the "GrBlue" style, buttons tend to look disabled and without an interactive response when the mouse goes over them they really look dead.


              There is a way to add visual effects to the login buttons. Here's my login screen that has the effects:


              Someone from Alpha could probably explain why the visual effects are not, by default, in the login component. But it is possible by altering the html before the server sends it to the browser.

              The solution I used involves injecting a couple of javascript functions in the login page and adding the mouse event attributes that the buttons are missing.

              My solution is not complete as it does not adopt automatically to changing of the project's style and it could be lacking in compatibility for older browsers.



              • #8
                Re: Login Component CSS

                You can change the Login Dialog with CSS. Have a look at my site
                Keith Hubert
                Alpha Guild Member
                KHDB Management Systems
                Skype = keith.hubert

                For your day-to-day Needs, you Need an Alpha Database!


                • #9
                  Re: Login Component CSS


                  I realize that you can change certain elements of the Login component with CSS which I have done to a great extent. However, as Jerry mentioned earlier in this thread the Login component does not support certain CSS selectors (i.e. ButtonHover, ButtonPressed). It appears the only button related selector supported is Button, which I can see that you have altered for your app. My intent was to have the button background change colors as well as have the border change when a user mouses over the login button.


                  • #10
                    Re: Login Component CSS

                    Mine changes color (please don't tell it it can' thinks it can)
                    I did this back in V9 and don't remember what I did. Just looked and don't see anything specific that I did, but I know for sure it didn't involve JavaScript

                    Pat Bremkamp
                    MindKicks Consulting


                    • #11
                      Re: Login Component CSS

                      Actually, Jerry Brightbill said, "The buttons on the login component do not currently support those styles." I do not think he was saying the styles are not supported, he was just saying the "buttons" do not support them. The styles are available to the Login component, but the javascript functions used to apply and remove these styles dynamically on the buttons as the pointer is moved over them is not. Pure in-line javascript could be written to add and remove the styles from the buttons, but it is simpler to have functions do this. Alpha is more qualified to explain the whole thing, but I will give it a try and please forgive me if I make a mistake...

                      Look at the following generated html for a button on the login component (cr/lf's added for clarity):

                      <input id="cptee_Login_submitbutton"
                      value="Login" name="submitbutton">

                      Now, look at the following for a button that appears on a form loaded after the login component:

                      <button id="CPTEE_SELE.V.R4._UNBOUND_BUTTON_1"
                      onclick="/* actionJavascript:dc7e2a09-73c2-4ac1-aa2d-98ba738f5b84 */ CPTEE_SELE_GridObj.ajaxCallback('G','4:all','OpenSelectDS','','_getData=true');"
                      style="margin-left: 4px; margin-right: 4px; cursor: pointer; "

                      Those "onmouse*" events give us the visual effects. But those events reference "$rcn" (Remove CSS Class Name from element) and "$acn" (Add CSS Class Name to Element) javascript functions that are defined in core.js To me, it appears core.js has not been loaded by the time the Login component displays. I don't know exactly when or how core.js gets loaded and I do not know why A5 does not load it for the login component.

                      So, in the solution I mentioned earlier, I define some javascript to perform the equivalent of "$rcn" and "$acn". Then I insert the missing "OnMouse*" events for the buttons before delivering the html to the browser. My a5w login page fixes-up the button definitions created by Alpha. In my running app the "login" button appears as follows to the client browser (again, cr/lf added for clarity):

                      <input id="cptee_Login_submitbutton"
                      class="GlassOliveButton "
                      style="margin-left: 4px; margin-right: 4px; cursor: pointer; "
                      onmouseout="removeClass(this,'GlassOliveButtonPressed');removeClass(this,'GlassOliveButtonHover');" name="submitbutton">



                      • #12
                        Re: Login Component CSS


                        Your analysis is correct. The login component is an older legacy component that was updated to allow the use of V11 styles. At that time, we did not add any JavaScript events to capture mouseover or onclick events. The login component has been slated for an upgrade for some time to bring it more in line with the more modern components, but since the issues with it are primarily cosmetic and it has a very singular use that it does well with very low overhead, it is a very low priority project. There is also the matter of what will happen to it when we move to the IIS environment and until that is resolved, we don't want to spend valuable time upgrading it now.

                        The JavaScript support files are not loaded by the Login component as it is not Ajax enabled. However, you can load all of the required functions by adding this to the page that contains the login component.
                        HTML Code:
                        <script type="text/javascript" src="javascript/a5.js"></script>
                        If that page has any other components, that file is probably already being added by the other component code.
                        Last edited by JerryBrightbill; 03-18-2012, 10:14 PM.


                        • #13
                          Re: Login Component CSS

                          Oh, thank you Jerry for that clarification.

                          I have the visual effects working in my Version 11 Login component.

                          See video example in post # 7, above.



                          • #14
                            Re: Login Component CSS

                            Hey Rich,

                            Where... how... do you get your javascript into the login a5w page? If you could outline the steps you go through to get the code in I would really appreciate it. Thanks. This might help to solve another issue I'm having.

                            EDIT: Do you put the javascript code into the Freeform Edit region of the login component? Replacing the {SubmitButton}?
                            Last edited by Davidk; 05-27-2012, 01:10 PM.


                            • #15
                              Re: Login Component CSS

                              I did all the mods by changing the a5w page, as the login component seems to lack just about every option that other components have. I attached my login.a5w page so you can see exactly what I did. View the file in source mode. Notice the following line in the page:
                              currStyle = "GrBlue" ' How do we get current project's style???

                              Does anyone know how to substitute in the current project's style instead of hardcoding "GrBlue" on that line?

                              -Rich Fulham
                              Attached Files