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

Opening Bugged Component

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

    Opening Bugged Component

    I have a UX component that, when opened, crashes Alpha. I don't mind remaking it, but I would like to be able to open it or at least view it in some way, so I can look at the JavaScript code that I wrote and use it in the remake. I submitted a bug report on this since I do not recall having any issue with this component prior to the update, and it has not been touched since a week before the update.

    Is there any way for me to retrieve the code from this file?


    NOTE: The file below crashes my version of Alpha (Developer Edition, V 12.3, Build 2689, Addins: Build 4440). Someone with more Alpha experience might be able to shed light on the full scope of an issue like this, but even though I have not seen any further damage caused by opening this file, I still advise caution to be used if you try to open this.
    OLDContacts.a5wcmp
    Last edited by BCJack; 02-09-2015, 01:54 PM. Reason: Added Note

    #2
    Re: Opening Bugged Component

    Open it in Notepad and browse around. You will find your custom code. Is it possible you are trying to open a published copy of the UX. Publishing over your development files is a common mistake for newer users.
    Steve Wood
    See my profile on IADN

    Comment


      #3
      Re: Opening Bugged Component

      Thanks Steve, that worked.

      In response to your question, I am not sure really. I have several other UX components in the same location that open just fine, and I have published both locally and on our ZebraHost server without issue. Does that help eliminate that possibility?

      Comment


        #4
        Re: Opening Bugged Component

        It is unlikely with what you describe.
        Steve Wood
        See my profile on IADN

        Comment


          #5
          Re: Opening Bugged Component

          Did you see if Alpha has been making backup copies of the component automatically as you save it? Right-click it in the component list and select "Restore Backup". It will show you the previous copies it has made of the component, if any, and you can pick one to restore.

          Comment


            #6
            Re: Opening Bugged Component

            Excellent! Thanks Rich.

            Comment


              #7
              Re: Opening Bugged Component

              Jack,
              BTW, components used to go bad on me, like that. Excluding the development folders from an automatic backup that was running whenever files were changed eliminated most issues. The other fix may have been Alpha improvements, but that was a few years back. If you have another automatic backup program running I would set it to exclude your alpha development folders. Then configure alpha to prompt you to make a zip backup of the whole project the first time it is opened in a day. Have Alpha place that .zip backup in a location that your other backup software can backup on a timed scheduled. Go to "View Settings" Workspace / Backup, checkmark "Require periodic backup..... 1 day". This backup is in addition to the one I mentioned in post # 5.

              Comment


                #8
                Re: Opening Bugged Component

                Now that you mention it, the folder where all my development files are stored is actually in a folder that is automatically backed up by Google Drive. I guess I will need to remove them from this folder and instead have the zip backups go in to the Drive folder instead.

                Thanks again Rich, I have a feeling this will save me a lot of headache in the future.

                Comment


                  #9
                  Re: Opening Bugged Component

                  I have used Cobain Backup for many years. I backup my projects around 2AM, but I am often working on the same projects that are being backed up. Never had any problem at all. If this is the only corrupt component (if that is what it is), I would not necessarily suspect your backup. Google for similar issues with Drive.
                  Steve Wood
                  See my profile on IADN

                  Comment


                    #10
                    Re: Opening Bugged Component

                    This one component in particular was crashing 100% of the time, but every now and then I get an application crash when trying to save other components, or creating new ones. Such a crash used to be once a week, but now after the most recent update, seem to be 10 or more times a day. I am wondering if this last release was a bit buggy or if my project is slowly getting corrupted.

                    Also, after submitting a bug report on that crashing component, I received a reply stating that it was caused due to a Tab control inside a Panel Card AND the last control in the Tab Pane being Hidden. I had this setup twice in that component. They said it would be in the pre-release notes soon.

                    Comment

                    Working...
                    X