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

Code Library Editor

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

    Code Library Editor

    zCodeLibrary provides an editor for Code Libraries used in the Code Editor. This editor uses an A5 table and form to edit the contents, making all the A5 features for editing data available.

    To view the Code Libraries from the menubar in the Code Editor, select Task List -> Code Library.

    You can create your own Code Library. I've done this, and I refer to it quite frequently. However, I've observed the following limitations with the built-in editing.

    - Deleting entries corrupts the Library.

    - No way to search the library.

    - No easy way to do search and replace in the library.

    The following scenario was the impetus for zCodeLibrary. I originally named the parameters for xDialogs the following DialogTtl, Dialog, Code. The documentation will show these variable names used in very early code samples. After some time and conflicts in variable names, I decided a better naming convention would be DlgTitle, DlgBody, and DlgCode. You will also see these conventions used in the documentation code samples. I made the changes in the code snippets I could identify, but without fail, I used a code snippets with the old naming convention. And as luck would have it, the snippets would have seldom used code paths such as error handlers. So, the introduced problem wasn't identified until much later and only after the out-of-date code snippet was used in many other places.

    Because I have invested so much time in my Code Library, I figured I could justify some time developing a better way to edit the contents. It took much more time than anticipated, but I also figured out a neat way to package it as a single function that could recreate the required table and form in the current database.

    You only need to import the function in zCodeLibrary.txt to use this code. In the Code Tab of the editor, right-click anywhere and select Import from the context menu.

    Next, call the function from the Interactive Window with no parameters; enter the following: zCodeLibrary()

    This will open the Code Library Editor form. The required table and form will be built into the current database on the first run call to the function. If you are using Code libraries, the form's functionality should be self-explanatory with the following caveat.

    When Edit Code is used, the code of the current record is edited as a function named zzCode in a Modeless dialogue. While zzCode is open, you can still interact with the Code Library Editor form. A timed event on the form will look for the closing of the Code Editing dialogue. When it is closed, the saved code version is placed back into the form, but only if the same snippet is selected. So do not move to a different record or change the snippet name until the Save button in zzCode Dialog is used and the zzCode dialogue is closed.

    zCodeLibrary can also be installed as an Addin, making it available for any of your projects.

    From the Control Panel Menubar in Desktop applications, select Tools->Addin Manager
    Click the link: Open Addins Folder
    click the button: Open system folder
    It is NOT recommended you use: Open user folder
    Copy file ZCODELIBRARY.AEX to the folder that is opened.

    The addins folder may not be created during the installation of AlphaAnywhere. It will be created the first time you attempt to access it via these menus. But, because the addins folders are under the program folder, they can only be created by alpha5.exe if it is Run as administrator. Right-click on alpha5.exe in the file manager and select Run as administrator from the context menu. Then, follow the steps above.

    To make the Addin available from the Code Editor Menubar, Code -> Addins. Copy the file zCodeLibrary.code_editor to the folder c:\Program Files (x86)\a5V12\Control_Panel_Addins\

    The Code editor will need to be closed and reopened before the Code -> Addins menu option is visible.

    The folder c:\Program Files (x86)\a5V12\Control_Panel_Addins\ contains the file How to Create Control Panel Addin Menus.Txt that further explains the format of the *.code_editor file.

    ** OUTSTANDING ISSUES **

    If you remove the zCodeLibrary table and then attempt to rebuild in the same session using this script you may get errors. Restart Alpha5 before rebuilding the zCodeLibrary table and form.

    After initial build of table and form a single mouse click anywhere is required to display the form.
    Attached Files
Working...
X