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

FYI: An alternative to creating Global Functions

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

  • FYI: An alternative to creating Global Functions

    a user asked me this question:

    "i want to define a bunch of functions that can be used in multiple places, but I don't want to make each function into a global function (i.e. a function that is visible in the code tab of the control panel)"

    the solution is the xbasic compile_template() function.

    here is the answer i sent him:

    here is one way to define a whole bunch of functions that can be used in multiple places without having to make each function into a udf.


    1. define a string that contains all of the function definitions.

    string = ""%code%
    function foo as c ()
    ui_msg_box("","This is foo")
    end function

    function foo2 as c ()
    ui_msg_box("","This is foo2")
    end function

    function foo3 as c (name as c )
    ui_mg_box("","Hello : " + name)
    end function
    %code%

    2. when you want to use the functions in your code, get a pointer to them:

    dim p as p
    p = compile_template(string)

    3. to use a function, just call it, using the pointer as a prefix

    e.g.

    p.foo()
    p.foo2()
    p.foo3("name")

  • #2
    RE: FYI: An alternative to creating Global Functio

    Selwyn,

    This could be very useful!

    1) What "scope" should be given to the pointer "p" if we want the functions to be "visible" throughout the app? i.e. to avoid having to "re-compile" the string each time we want to use one of its functions.

    2) It sounds as though the "string" could be stored in a memo field and retrieved for "compilation" in an autoexec script. Is that right?

    -- tom

    Comment


    • #3
      RE: FYI: An alternative to creating Global Functio

      you could make the pointer global if you wanted.

      you can give the pointer any scope that you want. it is just an a5 variable.

      compile_template() is very fast, making the pointer a local variable, and then doing compile_template() in each script that uses the functions is not going to result in a performance hit.

      Comment


      • #4
        RE: FYI: An alternative to creating Global Functio

        Also keep in mind that, because it's a A5 pointer, they can be passed along to functions, as needed....

        funcs = ""%str%
        function foo as c ()
        end function
        %str%

        dim p as p
        p = compile_template(funcs)
        bar(p)


        function bar as c ( pFuncs AS P )
        bar = pFuncs.foo()
        end function
        Aaron Brown
        Alpha Software Development Team

        Comment


        • #5
          RE: FYI: An alternative to creating Global Functio

          Thanks...
          Marcel

          I hear and I forget. I see and I remember. I do and I understand.
          ---- Confusius ----

          Comment


          • #6
            RE: FYI: An alternative to creating Global Functio

            Is there any practical difference between defining a group of functions this way vs. as a class?

            define class fooclass
            function foo as c ()
            ui_msg_box("","This is foo")
            end function

            function foo2 as c ()
            ui_msg_box("","This is foo2")
            end function

            function foo3 as c (name as c )
            ui_msg_box("","Hello : " + name)
            end function
            end class

            One thng I have noticed about a class is that Dim Private variables do seem to be public, e.g.
            ?p.myprivatevar gives a value.

            Bill.

            Comment


            • #7
              RE: FYI: An alternative to creating Global Functio

              A class is a very different concept. Classes can be instantiated, be inherited, define interfaces, contain public and private members....

              For very very basic use, they do resemble each other, but they way they are implemented and used ends up being rather different.
              Aaron Brown
              Alpha Software Development Team

              Comment


              • #8
                RE: FYI: An alternative to creating Global Functio

                I have not been able to create a private variable. If in a class definition I
                ...
                DIM private myvar as c
                myvar="a"
                ...

                then dim the class and get a pointer p to it.
                ?p.myvar should not return a value, but it does. The only variables that are not visible are local variables in a function of the class. But there is not much documentation on classes/interfaces.

                Bill.

                Comment


                • #9
                  RE: FYI: An alternative to creating Global Functio

                  You're right, Bill. Currently private variables aren't private. Classes are not fully implemented, but be assured that in the future, A5 will be moving to a more Object Oriented Design and the class support will become very robust.

                  My point is simply that compile_template() is very different conceptually than a class.
                  Aaron Brown
                  Alpha Software Development Team

                  Comment

                  Working...
                  X