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

refreshing while testing on localhost not always refreshing

  • Filter
  • Time
  • Show
Clear All
new posts

  • refreshing while testing on localhost not always refreshing

    I really thought this would be so simple, but apparently it is not (for me anyway).

    I'm creating a UX component that will open and populate with a grid row's data when I click on the button in the grid. It is working, no that was more to paint a quick picture.

    In the UX, I chose to add another textbox. I mapped it to a field in a table like the original 3 textboxes were mapped. I hit save then publish. I go to my browser and refresh the localhost page. I click my customers button and get to the grid. I click the button in the row, and now I have 4 textboxes. The 3 original and the new one. The 3 original have mapped data, however the 4th does not.

    I went back to Alpha, click publish, then made sure it said "All files in project," cleared publishing history, unchecked "publish new or modified files only," and hit "publish" again. Then on my browser I did Control plus F5 to refresh. Same problem. I stopped the development server and restarted it. Same.

    So I figured maybe there was a hiccup in Alpha. I removed the button from grid and deleted the UX component (there were only 4 textboxes, so its quick and easy). Published, etc. The button was still there. I did the whole publish thing and refresh thing again. Same. So then I banged my head on the wall, poured a drink (water; its a work day), and walked outside. When I came back in, I tried it again, and the button was now gone.

    Okay, good, I recreated the UX with 1 textbox. Perfect. Data appeared in it. Then I created textbox 2 and 3, publish, worked perfect. Added a 4th textbox (mapped to a different field than in the beginning), and nothing.

    I think it has to be a matter of not completely refreshing or publishing. Am I missing something?

    Alpha Build 6012

  • #2
    Re: refreshing while testing on localhost not always refreshing

    You can't depend on a browser refresh for localhost. It used to work without fail, but not any longer... not for at least a year. If you're making minor client-side UX changes... styling, etc. and running live preview, then a refresh works most of the time. However, any server-side, data work will require a publish and re-running the component.

    If you're working with a grid then you should always publish and run as a refresh almost never works.


    • #3
      Re: refreshing while testing on localhost not always refreshing


      I again deleted the entire UX component and button from the grid. I recreated it now with 5 textboxes initially, and they all populated as expected. I then added 1 UX and published, refreshed my browser and checked it out via localhost. The initial 5 populated and the next one did not.

      You said it would require a publish and rerun the component. I think I did that. I click publish and have it publish the entire project (not just changes). I refresh the browser. I have even cleared the cache, ctrl F5, etc. Is there another way that I should be doing the publish and rerun the component?


      • #4
        Re: refreshing while testing on localhost not always refreshing

        Refreshing the browser doesn't work. You've not said how you're running the component. Create an A5W page for the main component, right click that A5W page from the Web Projects Control Panel, and choose "Publish (Local Webroot) and open". Doing this you're running the component fresh each time... and all changes will show.

        As said, Grids were always hit and miss... mostly miss. UX components would refresh without trouble. About a year ago, maybe a bit longer, you could no longer depend on refreshing UX components... depending on the change. So, it safer, and faster now, to just re-publish and open fresh.


        • #5
          Re: refreshing while testing on localhost not always refreshing

          The UX component is called from a button in a customer grid row. The UX component is populated with the customer data from the row. The grid row is opened by a button on a page layout which is set on an a5w page. That is set in a tabbedui that is on its own a5w page.

          Hopefully all of that makes sense. I'm about 2 months in with AA, and I making it based on videos and examples I have seen.


          • #6
            Re: refreshing while testing on localhost not always refreshing

            Start with the TabbedUI A5W page each time... Publish to Localhost and Open. After you make changes to your Grid and/or UX and publish, then publish and open your TabbedUI A5W page.


            • #7
              Re: refreshing while testing on localhost not always refreshing

              I tried the right click and publish way like you said in #4 above. Then as in #6. The UX continues to consistently populate the original textboxes I created, but it will not populate the one that I added after. Really is odd. I even went so far as to stop the development server and restart, I cleared cookies and cache in the browser, I ran it in IE (I previously only did it in Chrome), and I rebooted my computer.

              I would still love to know how to solve it, but as a poor workaround I deleted the UX and created one with a textbox for every cell in the referenced table. Then I'll just delete one if I no longer find it useful. That was an easy enough bandage for tonight, however if I add 1 field to the table and add a textbox to reference it, I'll be in the same situation again.


              • #8
                Re: refreshing while testing on localhost not always refreshing

                Could be a bug... 6012 is just chock full of them... it's a mess. Try the latest pre-release.