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

How Miserable are Tree Controls?

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

    How Miserable are Tree Controls?

    I worked up this example for testing - try it in the IW, works great:
    Code:
    dim images as c
    dim list as c
    dim vList as c
    images = <<%str%
    $$mini.folder
    $$mini.file.open
    $$generic.preview
    %str%
    list = <<%str%
    1+2cat1.3{DATA=Report to Preview}A
    1+2cat1.3B
    1+2cat1.3C 
    1+2cat1.3{DATA=Report to Preview}D
    1+2cat2.3E
    1+2cat2.3F
    1+2cat2.3G
    1+2cat2.3H
    %str%
    result=ui_dlg_box("Simple Tree",<<%dlg%
    [%I=@images%.30,15vlist^<list] |<OK>;
    {ysize=1}
    [.30vlist]
    %dlg% )
    Then using a table of reports, I tried to make an XD tree, adding fields to hold the image numbers I need.
    In the IW my tree data looks correct:
    Code:
    auto_list_vtree = table.external_record_content_get("replist","lvl1+alltrim(group)+\".\"+alltrim(lvl2)+\"{data=\"+alltrim(dictname)+\"}\"+display","group+display")
    
    ?auto_list_vtree
    = 1+2ACT_MENU.3{data=Act Menu Rep@c:\a5v11\skkv11\act_menu.ddd}Act Menu Rep
    1+2A_HELP.3{data=Prn Help@c:\a5v11\skkv11\a_help.ddd}Prn Help
    1+2A_HELP.3{data=Quick Prn Help@c:\a5v11\skkv11\a_help.ddd}Quick Prn Help
    1+2B_MSGREP.3{data=Msg Code Matrix@c:\a5v11\skkv11\b_msgrep.ddd}Msg Code Matrix
    1+2DIRECTORY.3{data=Dir Phone List@c:\a5v11\skkv11\directory.ddd}Dir Phone List
    1+2INVOICE.3{data=Invoice@c:\a5v11\skkv11\invoice.set}Invoice
    1+2INVOICE.3{data=Quick Invoice@c:\a5v11\skkv11\invoice.set}Quick Invoice
    Here is the script:
    Code:
    dim images as c
    DIM vtree as C
    
    images = <<%str%
    $$mini.folder
    $$folder.open
    $$generic.preview
    %str%
    dim auto_list_vtree as c
    auto_list_vtree = table.external_record_content_get("replist","lvl1+alltrim(group)+\".\"+alltrim(lvl2)+\"{data=\"+alltrim(dictname)+\"}\"+display","group+display")
    'msgbox("",auto_list_vtree,0)
    'end
    temp_count = w_count(auto_list_vtree,crlf())
    DELETE a_vtree
    DIM a_vtree[temp_count] as c
    a_vtree.initialize(auto_list_vtree)
    ok_button_label = "&OK"
    cancel_button_label = "&Cancel"
    varC_result = ui_dlg_box("Alpha Five",<<%dlg%
    {region}
    Type prompt here:;
    [%D=".";I=@images%.40,25vtree^<a_vtree];
    [.40vtree];
    {endregion};
    {line=1,0};
    {region}
    <*15=ok_button_label!OK> <15=cancel_button_label!CANCEL>
    {endregion};
    %dlg%)

    But when running this simple tree control script, this is what I get:

    The tree should be displaying just the DISPLAY name and the text box below the actual path to the report.
    Attached Files
    Last edited by MoGrace; 08-20-2015, 10:14 PM.
    Robin

    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

    #2
    Re: How Miserable are Tree Controls?

    I spent most of the day on this freaking script to display in an embedded XD on a form - my error is using "." for the D directive, since the text also has a "."; so I tried "^" instead - and of course now it works fine!
    Robin

    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

    Comment


      #3
      Re: How Miserable are Tree Controls?

      Hi Robin,

      The problem is the "." contained in your DATA section. More specifically the period in your filename preceding the file extension. The tree control is reading this as a delimiter for the tree data. You can change the delimiter used in the control setup in the xdialog code. Pick a character that you won't need in menu data and then make sure you never use it. In one tree i developed based on user entered data I created data entry rules to keep it out of the data and also a routine to check the data on the way into the tree and remove that character if it snuck past.

      [%D=".";I=@images%.40,25vtree^<a_vtree];

      EDIT: Too slow. I was responding while having lunch. Glad you got it. Been there done that.
      Tim Kiebert
      Eagle Creek Citrus
      A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

      Comment


        #4
        Re: How Miserable are Tree Controls?

        Hi Tim,
        Glad you're here. I was looking at a new release of Fishbowl Inventory (a Quickbooks product), and really like the web style components they are using.

        Especially interesting was a Tree Control of grouped reports that when one is selected, displays in a preview window. I think the use of 2 supercontrols on a form could achieve this same functionality. I have the script that populates a table for the tree control, and am now working on passing the full report path to the Report preview supercontrol.

        One other thing they are doing at Fishbowl is saving filters for their reports to a table, and also use a popup form for the record selection.

        This project is going to be a major undertaking to get it to work in a similar fashion - but definitely doable for the desktop.

        FB_Reports.png

        What I have so far: report_menu.png
        Last edited by MoGrace; 08-21-2015, 01:57 PM.
        Robin

        Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

        Comment


          #5
          Re: How Miserable are Tree Controls?

          Wow Robin.. What you have so far looks great. I can see I am going to have to pick your brain on this.

          Comment


            #6
            Re: How Miserable are Tree Controls?

            Hi Preston - you do know the FB png is only an example...I wish it were mine!

            I've gotten sidetracked with my runtime issues - but will get back to this project when I have more time - stay tuned!
            Robin

            Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

            Comment


              #7
              Re: How Miserable are Tree Controls?

              Originally posted by MoGrace View Post
              Hi Preston - you do know the FB png is only an example...I wish it were mine!

              I've gotten sidetracked with my runtime issues - but will get back to this project when I have more time - stay tuned!
              I was talking about the "What I have so far: report_menu.png".

              Is that not yours?

              Comment


                #8
                Re: How Miserable are Tree Controls?

                Why yes, yes it is!
                Robin

                Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

                Comment

                Working...
                X