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

fadeoutMessage Display Issue

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    fadeoutMessage Display Issue

    Hello,

    I'm trying to use a simple fadeoutMessage in a placeholder that includes style attributes. If I use the Style property it has no effect. If I use the Class property the container will appear the first time the panel is rendered, but without text and without fading. The message then operates normally after the first time it's activated with an actual message. I couldn't find any documentation or video that addresses this issue. I also thought to change the default style in a local version of MobGray but couldn't identify the style that applies.

    I was concerned that it might be some type of interference in my app, but the same behavior occurs in a simple single panel scratchpad with nothing more than a button and the placeholder field.

    This is a mobile app compiled with Alpha Build 5159 and it occurs under Working Preview as well as on Android and iOS.

    Any thoughts?
    Thanks,
    Joe
    Tags: None
    #2
    Re: fadeoutMessage Display Issue

    The problem is that, for some reason, Alpha shoves in a style for a placeholder... overwriting whatever you've set. The rendered Placeholder looks like this...

    Code:
    <div class="A5CWLayout" style="width: " id="DLG1.V.R1.PLACEHOLDER_2">
</div>
    No matter what Style you set, Alpha overwrites it... or ignores it... and you end up with the above.

    Using a Class almost helps... as you've seen... but you start out with an empty placeholder. For example, if you had put a border on the placeholder, you'd end up with a little box.

    While the Fadeout message is performing... the style gets appended with an opacity setting... decreasing in value until the time runs out. Then opacity gets removed and display:none; gets added.

    The bug here is that Alpha should be appending their "width: " (which is an invalid property value) to your style... not replacing your style.

    A workaround is to set the style of the placeholder after it's rendered... so that you're clobbering Alpha's setting... instead of them clobbering yours.

    E.g. in onRenderComplete...

    Code:
    var ph1 = {dialog.Object}.getPointer('PLACEHOLDER_1');
ph1.style.display = 'none';
ph1.style.color = 'red';
ph1.style.fontSize = '24px';
ph1.style.borderStyle = 'solid';
ph1.style.borderWidth = '1px';
ph1.style.borderColor = 'blue';
    If you set display to none first, then you shouldn't see the placeholder during render. In this case, you've hidden the placeholder, set it's color and border, etc. When the message is run, Alpha will remove your display:none;... opacity is added to the style... and when the counter is done... opacity is removed and display:none; is added back;

    The odd thing is... that original "width: " Alpha shoves in is removed and never put back. It's showing as Invalid upon render... and really should never be there in the first place. If it wasn't there, you wouldn't have had an issue.

    You should report this to Alpha and get them to take out their invalid css.
    Last edited by Davidk; 08-13-2018, 10:00 PM.

    Comment

      #3
      Re: fadeoutMessage Display Issue

      Thank you very much for the response and clarity. I will file a bug report with Alpha.

      Comment

        #4
        Re: fadeoutMessage Display Issue

        David,
        I think you may be on to something. The last update broke a lot of the CSS styles. It seems like Tabs/accordion and Modern Frames aren't working as before. There may be other stuff too.

        Comment

          #5
          Re: fadeoutMessage Display Issue

          This issue has been around for at least the last several "official" releases... is isn't anything new.

          Comment

            #6
            Re: fadeoutMessage Display Issue

            This is probably true. I hadn't updated for a while. I sent in a test case to Alpha, but they haven't been able to reproduce it. This is what I'm seeing... https://www.screencast.com/t/thY3TnKuY

            Comment

              #7
              Re: fadeoutMessage Display Issue

              David,

              Thanks again. I have implemented your workaround in the onRenderComplete event and it functions perfectly. For any others that might experience this issue, I only used the ph1.style.display = 'none' without the style attributes in the event for each of the placeholders on different panels. The Class definitions in the local CSS are then applied correctly to each of the placeholders.

              Comment

              Previous template Next
              Working...
              X