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

Pre-Release Build 3711-4690 3-Jul-2016 killed my UX controls - Take care..

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

    Pre-Release Build 3711-4690 3-Jul-2016 killed my UX controls - Take care..

    Every - live and working preview..
    Error:Script:a5dialoghelper_arguments_to_stateObject() line:22 Extra characters at end of expression
    Peter
    Insanity: doing the same thing over and over again and expecting different results.
    Albert Einstein, (attributed)
    US (German-born) physicist (1879 - 1955)

    #2
    Re: Pre-Release Build 3711-4690 3-Jul-2016 killed my UX controls - Take care..

    That is the nature of pre release builds. You never know what happens.

    But good that we have developers who test them .

    Comment


      #3
      Re: Pre-Release Build 3711-4690 3-Jul-2016 killed my UX controls - Take care..

      Yea - agree - great to have access, but extremely important as a fix until an official releases are made.
      Insanity: doing the same thing over and over again and expecting different results.
      Albert Einstein, (attributed)
      US (German-born) physicist (1879 - 1955)

      Comment


        #4
        Re: Pre-Release Build 3711-4690 3-Jul-2016 killed my UX controls - Take care..

        Need google maps fix Urgently ...
        Can't afford to play around with pre-release
        Please update official release alpha !!!

        Comment


          #5
          Re: Pre-Release Build 3711-4690 3-Jul-2016 killed my UX controls - Take care..

          Send an email to Selwyn - if you don't have the email use the bug fix process in help - that gets attention very quickly. I think you will find then very accommodating as the Google thing is a REAL BIG issue.
          Insanity: doing the same thing over and over again and expecting different results.
          Albert Einstein, (attributed)
          US (German-born) physicist (1879 - 1955)

          Comment


            #6
            Re: Pre-Release Build 3711-4690 3-Jul-2016 killed my UX controls - Take care..

            Originally posted by peteconway View Post
            Every - live and working preview..

            Peter
            Not the case here. No issues with Live Preview or Working Preview under 3711-4690. Is this something you reported and had confirmed?

            Comment


              #7
              Re: Pre-Release Build 3711-4690 3-Jul-2016 killed my UX controls - Take care..

              Originally posted by Davidk View Post
              Not the case here. No issues with Live Preview or Working Preview under 3711-4690. Is this something you reported and had confirmed?
              Same as David, not having those issues with build 3711-4690 Pete.
              Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

              Comment


                #8
                Re: Pre-Release Build 3711-4690 3-Jul-2016 killed my UX controls - Take care..

                Well - I did report it an did not get a response, so I suppose you either get the problem or you don't - I do.
                Cheers. I've rolled back.
                Insanity: doing the same thing over and over again and expecting different results.
                Albert Einstein, (attributed)
                US (German-born) physicist (1879 - 1955)

                Comment


                  #9
                  Re: Pre-Release Build 3711-4690 3-Jul-2016 killed my UX controls - Take care..

                  i am not able to duplicate the error and there are no other reports from anyone else.


                  i can't duplicate any problem

                  the a5dialogHelper_arguments_to_stateObject() function was modified last week, but it appears to be correct to me.

                  here is a test you can run at the interactive window


                  Code:
                  
                  dim args as sql::arguments 
                  args.add("FirstName","fred")
                  args.add("LastName","smith")
                  dim tmpl.arguments[2] as p
                  tmpl.arguments[1].name = "FirstName"
                  tmpl.arguments[2].name = "LastName"
                  
                  txt = a5dialoghelper_arguments_to_stateObject(args,tmpl)
                  
                  showvar(txt)
                  
                  you should get this:
                  {dialog.object}.setStateInfo({ 	__args_C_FirstName: 'fred', 	__args_C_LastName: 'smith' })

                  if you get the error, then it would appear that something went wrong with your install and you should reboot and reinstall the latest pre-release.

                  Comment


                    #10
                    Re: Pre-Release Build 3711-4690 3-Jul-2016 killed my UX controls - Take care..

                    Many thanks to you guys for looking into this, i'll re-install and run the test and come back to everyone.
                    It may be an idea to set up a section on the message board for pre-release users to provide feed back without alarming official release users.
                    Pete
                    Insanity: doing the same thing over and over again and expecting different results.
                    Albert Einstein, (attributed)
                    US (German-born) physicist (1879 - 1955)

                    Comment


                      #11
                      Re: Pre-Release Build 3711-4690 3-Jul-2016 killed my UX controls - Take care..

                      OK - here is the video of the tests and the issue - only takes a few minutes, starts with the problem, the test, then previous build and them a clean install of the 4690.

                      http://screencast.com/t/fDiiQs59

                      The round Trip Video - http://screencast.com/t/4OFUOL0f211

                      Selwyn - ill send you my component.

                      The component working
                      2016-07-06_1118CSS.png
                      Last edited by peteconway; 07-05-2016, 09:19 PM.
                      Insanity: doing the same thing over and over again and expecting different results.
                      Albert Einstein, (attributed)
                      US (German-born) physicist (1879 - 1955)

                      Comment


                        #12
                        Re: Pre-Release Build 3711-4690 3-Jul-2016 killed my UX controls - Take care..

                        thanks for sending the component. turns out that the 'bug' is actually on your side. your component defined several arguments and you have a duplicate argument name in your arguments definition.

                        not sure how you managed to do this as the define arguments dialog checks for duplicate names.

                        regardless, if you fix your component and remove the duplicate argument definition, it will work.

                        Comment


                          #13
                          Re: Pre-Release Build 3711-4690 3-Jul-2016 killed my UX controls - Take care..

                          Well Selwyn came back to me - it was my bad that was revealed by a recent change to AA.
                          This from Selwyn.

                          Re: Build 3711-4690 3-Jul-2016 killed my UX controls
                          selwyn Rabins 12:14 PM Flag this message Photos
                          To: Peter Conway

                          thanks

                          i can duplicate the problem, but the issue actually lies on your side.

                          if you look at your argument definition, you have a defined InclusingClassID twice.

                          before we made a change to to the a5dialoghelper_arguments_to_stateObject() this would not have mattered.
                          but we made a change to this function to address another issue and not you are getting caught by what was previously a benign bug on your part.

                          if you remove the duplicate definition your List will work.

                          I have changed the code so that it is impervious to duplicate argument names.
                          Insanity: doing the same thing over and over again and expecting different results.
                          Albert Einstein, (attributed)
                          US (German-born) physicist (1879 - 1955)

                          Comment


                            #14
                            Re: Pre-Release Build 3711-4690 3-Jul-2016 killed my UX controls - Take care..

                            Amazing service.
                            Insanity: doing the same thing over and over again and expecting different results.
                            Albert Einstein, (attributed)
                            US (German-born) physicist (1879 - 1955)

                            Comment

                            Working...
                            X