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

UX method indirection

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

    UX method indirection

    Code indirection is common in xbasic. Is it possible to do the same thing with UX methods?

    Code:
    {dialog.Object}.setValueFrom('ADBID2','list::Person_list::Adbid');
    {dialog.Object}.setValueFrom('PERSONID2','list::Person_list::PersonId');
    {dialog.object}.runAction('open_PersonDetail');
    This is on an event in a list. I want to replace Person_list with the name of the current list, so it is more generic.

    #2
    I am assuming you want to have a function, say an event that calls a global function in the UX that is written in a generic way such that you can tell that generic function to change one of the properties using a variable passed in.
    IE the things calling it change, but the function producing the end result can be written in a way to not need to be change and be universal.
    I do this to be able to have standard functions that call a different primary key and list name that is headed to an argument or state.

    Here is an example:


    Code:
    In an on select event of a list:
    
    FunctionList = 'CUSTOMERSLIST';  //The name of the List in the UX
    FunctionHandle = 'CustomerID';  //The column name of the primary key of that list
    setStateBro(FunctionList, FunctionHandle);
    
    The generic function being called:
    
    function setStateBro(FunctionList, FunctionHandle) {        
    
    var listObj = {dialog.object}.getControl(FunctionList);
    var selectionData = listObj.selectionData[0];
    var Customer = selectionData[FunctionHandle];
    
    
    /*
    Construct an array object and send it all to state.
    */
    var obj = {};
        obj['svFunctionList'] = FunctionList;
        obj['svFunctionHandle'] = FunctionHandle;    
        obj['svCustomer'] = Customer;                                  
    
    {dialog.object}.setStateInfo(obj);​
    ​}

    Comment


      #3
      That is helpful, but not quite what I needed. Person_list is mentioned in the list onDblClick event
      Code:
      {dialog.Object}.setValueFrom('ADBID2','list::Person_list::Adbid');
      I would like to replace Person_list with a relative reference to the list, so the code will work regardless of what list it is in.

      Comment


        #4
        I think I do what you want, but I use viewbox controls instead of list controls.
        I have a habit of using several viewboxes, but I didn't 5 different functions (or even javascript actions)
        to populate 5 different viewboxes.

        It seems like you want a function where you can pass in parameters.

        Last but not least, you'll notice that I use PTR instead of Obj when I use {dialog.Object}.getControl();
        The reason is that EVERYONE that describes it states they are getting a pointer to the control, so I opt to name it PTR.

        Code:
        function listMagic( nameOfList) {
        {dialog.Object}.setValueFrom('ADBID2',nameOfList);
        {dialog.Object}.setValueFrom('PERSONID2',nameOfList);
        {dialog.object}.runAction('open_PersonDetail');​
        }
        Code:
        function initializeVB(vb,stateVar){
        // This code will populate individual viewboxes with the data from their respective stateInfo variable
        // The switch code will need to be adjusted for multiple viewbox controls
        //debugger;
        
        var vbPTR = {dialog.Object}.getControl(vb);
        var sourceData;
        switch(stateVar){
        case 'rawRxData':
            sourceData = JSON.parse({dialog.Object}.getValue('rxdata'));
            break;    
        }
        vbPTR.populate(sourceData,false,false);
        
        };​
        Gregg
        https://paiza.io is a great site to test and share sql code

        Comment


          #5
          I do this, but I only use one list per UX. I may show multiple lists on one page, but they are in their own lists that only populate when needed. With this, I only use list1 so I can take advantage of Alpha's prebuilt methods, and they are all universal. At that point, you can just create a single JavaScript Action that will work across all components.

          Comment


            #6
            Russell Craycraft The help you gave me with the one active list I have sometimes frustrates me, but today it's coming in handy.
            I'm working on having the on-click event load the detail, then populate and display a viewbox.

            Off topic, but are you Wasabi-CORS knowledgeable ?
            Gregg
            https://paiza.io is a great site to test and share sql code

            Comment


              #7
              Originally posted by Russell Craycraft View Post
              I do this, but I only use one list per UX. I may show multiple lists on one page, but they are in their own lists that only populate when needed. With this, I only use list1 so I can take advantage of Alpha's prebuilt methods, and they are all universal. At that point, you can just create a single JavaScript Action that will work across all components.
              Hi Russell… very nifty. This is my current mode as much as possible, with some limitations. Do you mind sharing your ux or code so I can improve mine? I can email you as well.

              Wayne

              Comment


                #8
                madtowng, Alpha can be frustrating no matter what. There's always going to be little issues. I have a client using a version from a couple of years ago, and now ways I'm used to doing things do not work, and I'm having to remember the little nuances. At least Alpha is actually developing out their platform though. Plenty of others don't, nor fix bugs as quickly, or offer good support.

                I really want to be in the JSON form realm, but will give it time to let Alpha develop it out before I invest my time learning it, (unless I have a need for a lightweight mobile app for a client, which may be coming up soon).

                I use Wasabi, but haven't set up CORS in quite a while. You may want to start a new post, and I (and others) can help out, then be able to easily reference it later too.

                Comment


                  #9
                  WayneH, I can share a UX and code, but not sure what you really need help with. If you want to email me, I can send you a Zoom link and show you some of my process if that helps. [email protected]

                  Comment


                    #10
                    Originally posted by Russell Craycraft View Post
                    WayneH, I can share a UX and code, but not sure what you really need help with. If you want to email me, I can send you a Zoom link and show you some of my process if that helps. [email protected]
                    Thanks for your time together on zoom today Russell. Lots of good ideas and encouraging on my current direction.

                    Comment

                    Working...
                    X