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

Version 4.4.5 TypeError style is undefined

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

    Version 4.4.5 TypeError style is undefined

    Searching for help to pinpoint an error I get in the latest build with 2 component which worked flawless in the previous official release.
    Both component are embedded in a page. In other components I don't get this error. Below screenshots live full preview under firefox with debugger and the lines from the component. Publiched to localhost gives the same error

    StyleErrorVersion445.PNGStyleErrorControlbar445.PNG



    I recreated the pages in the new build, still the same error.
    I changed the style form Alpha style to GrBleu, still the same error
    I stripped down suspected elements (controlbars in footers and all referencing code), no luck either
    Any suggestions whre to look before I will try to create a northwind sample and bugreport?


    Important: only then error message is annoying, the component runs fine when i close the message!
    thanks
    Ger Kurvers
    Alpha Anywhere / V4.6.1.9- Build 6488 (production) / V4.6.5.1 - 8722-5683(testing)
    Development: Mysql, windows 10 64 Applicationserver: standard on Windows server 2019

    #2
    Re: Version 445 TypeError style is undefined

    When you inspect your page, have a look in the Elements, Body, for a div with an Id ending "DEBUGUPDATECOMMANDS". This div is automatically added by Alpha.

    When a UX is run by itself in LivePreview, this div id resolves to 'DLG1.DEBUGUPDATECOMMANDS'. When the UX is embedded in a Page, in my case, the div id resolves to 'STEP.DEBUGUPDATECOMMANDS' because my UX is named 'STEP'. So... the div id must originally be '{dialog.componentname}.DEBUGUPDATECOMMANDS'.

    To what is your div id resolving? Can you post a sample page and UX? I have a feeling information is missing here.

    Comment


      #3
      Re: Version 4.4.5 TypeError style is undefined

      David, thanks for picking this up.


      I attached a stripped down component so that it can work without databaseconnection (originally it loads welcome logo and text and takes care for internationalisation). Beside the page and component I also added some icons and my style tweaks for the alpha style that is used. Just in case.
      The issue is still present.

      Components_Style_Issue.zip

      Maybe it is a new 'feature' of version 445 after all, from the prereleasenotes:
      UX Component - window.onerror Event Handler - In V4.5, the UX component generates a widow.onerror event handler to report Javascript errors. This event handler displays an alert with a full stack. In some cases, where you are loading 3rd party Javascript libraries, that might throw benign errors on loading, you might want to suppress this error reporting.

      The Capture detailed Javascript error information property allows you to turn off detailed Javascript error reporting.
      Unfortunately It is not working in this official release yet.
      Ger Kurvers
      Alpha Anywhere / V4.6.1.9- Build 6488 (production) / V4.6.5.1 - 8722-5683(testing)
      Development: Mysql, windows 10 64 Applicationserver: standard on Windows server 2019

      Comment


        #4
        Re: Version 4.4.5 TypeError style is undefined

        Ok... here's the problem... and a fix.

        Normally, Alpha shoves in a '{dialog.componentname}.DEBUGUPDATECOMMANDS' placeholder.

        However, as soon as you start using Panels... Alpha figures you're heading in a Mobile direction... and so it stops adding that placeholder. I'm just guessing at the reason, but the placeholder is no longer added.

        However, you are using a Server-side Action... "Populate Dialog from Tables..."... not something you'd be doing in Mobile. This Action has this in it's code...

        Code:
        "$('"+tmpl.alias+".DEBUGUPDATECOMMANDS').style.display = '';"
        So... Alpha is trying to set the style of a tag that doesn't exist.

        If you just want to fix this quickly... add a Static Text control to your UX somewhere... and enter this as the static text...

        Code:
        <span id="{dialog.componentname}.DEBUGUPDATECOMMANDS"></span>

        Comment


          #5
          Re: Version 4.4.5 TypeError style is undefined

          Awsome David, thanks a lot. Quick fix works as a charm, would never have figured this out myself!
          Ger Kurvers
          Alpha Anywhere / V4.6.1.9- Build 6488 (production) / V4.6.5.1 - 8722-5683(testing)
          Development: Mysql, windows 10 64 Applicationserver: standard on Windows server 2019

          Comment


            #6
            Re: Version 4.4.5 TypeError style is undefined

            There's another fix. In your Server-side Action, there is a property called "Show debugging information". You have this turned on. You can uncheck this option to solve the issue.

            Comment


              #7
              Re: Version 4.4.5 TypeError style is undefined

              David what planet are you from - nobody can know all this, lol - thanks again, I think this might help me as well!
              NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

              Comment


                #8
                Re: Version 4.4.5 TypeError style is undefined

                This is why sample components are so important. You can't report everything going on in a UX... there are thousands of combination features and properties. Ger's component acted the same way on my system... and so it was fairly straight forward to find out why.

                Comment


                  #9
                  Re: Version 4.4.5 TypeError style is undefined

                  ah, so true on the samples! I can't believe how much fun AS has turned out to be for me, the more I learn the more I want to learn...the more ideas and things I want to build, thanks again for your advice.
                  NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

                  Comment


                    #10
                    Re: Version 4.4.5 TypeError style is undefined

                    Originally posted by CharlesParker View Post
                    David what planet are you from - nobody can know all this, lol - thanks again, I think this might help me as well!
                    Haha, I thought it was just me thinking that
                    Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

                    Comment

                    Working...
                    X