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

Bug? Fields moving fr tabbed panel

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

    Bug? Fields moving fr tabbed panel

    --Alpha5v5trial
    --patch1354_1021

    --start with Contact Manager from Alpha4.5
    --add three new character field to people table
    --delete all fields from activity tab
    --rename activity tab
    --add the three new added fields to the renamed tab

    --make other changes to app (probably not relevant)

    --most things work fine, except:

    --run app
    --click renamed tab
    --click on one of the added fields
    --click A..Z on toolbar

    --wierd behaviour:

    --screen repaints, but shows first tab (not renamed tab)
    --but shows added field from renamed tab overlayed on first tab
    --overlayed field is not active; when it is clicked it disappears and the cursor jumps to another field on the first tab

    If its not a bug, let me know what to correct...
    If it is a bug... Good Luck

    Hasan

    #2
    RE: Bug? Fields moving fr tabbed panel

    Check how your fields are laid out. Are they touching each other or are they touching the edgs of the tabbed object. This will cause what you're experiencing.

    kenn
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    Comment


      #3
      RE: Bug? Fields moving fr tabbed panel

      Those fields aren't touching anything...

      However, there is a text object hidden behind the pane... I can see it in the object explorer but I can't find a way to delete it.

      Do you know a way?

      Comment


        #4
        RE: Bug? Fields moving fr tabbed panel

        if you can see it in the object explorer, select it in the object explorer. then click the select object button. the object on the form should now have a selection rectangle (assuming of course that the form is in design mode). then press the delete key. the object will be deleted.

        Comment


          #5
          RE: Bug? Fields moving fr tabbed panel

          That worked to delete the hidden text object... but the pane jumping field is still doing its thing.

          Comment


            #6
            RE: Bug? Fields moving fr tabbed panel

            Hasan,

            Does the form or its underlying table have any event-based code attached? If so, remove it and see if the problem is effected.

            Bill
            Bill Hanigsberg

            Comment


              #7
              RE: Bug? Fields moving fr tabbed panel

              need to see the data.
              can you zip your files and attach them to your reply, with info on how to repeat the problem.

              thanks

              Comment


                #8
                RE: Bug? Fields moving fr tabbed panel

                --Open the Contact Manager app
                --click the 'Keywords' tab
                --click inside the keyword field
                --click A..Z on toolbar
                --Error: the keyword field wiil jump to the first pane

                also,

                --Go into design mode move the 'Contact_type' field from the first tab to the last tab and repeat above steps for that field.

                Comment


                  #9
                  RE: Bug? Fields moving fr tabbed panel

                  I don't get things moving around from tab to tab but I do note an error due to the fact that the 255 length of the keywords field exceeds the maximum index key length.

                  Bill
                  Bill Hanigsberg

                  Comment


                    #10
                    RE: Bug? Fields moving fr tabbed panel

                    Yea... I've seen the 'too big for a key' problem... seems to me that Alpha Software ought to grey out the A..Z icon for such fields.

                    I'm puzzled about the 'pane jumping fields; acting up on my computer but not yours.

                    Oh well, after I get the app running I'll probably have to redo the layout from scratch to get rid of the problem.

                    Thanks,
                    Hasan

                    Comment


                      #11
                      RE: Bug? Fields moving fr tabbed panel

                      Hassan,

                      Try reducing the field length of keywords to whatever the maximum key length is; it's in the docs somewhere but I can't find it right now.

                      Secondly, why not go back to first principles and ask what the best way is to populate a field with several user-selected keywords. Your approach requires multiple entries in the same field by the user. My preferred method is a multi-select xdialog form based (as your lookup is) on a table. The xdialog is populated from the table. The user can make multiple selections from it in a single operation. The resulting choices go into a variable and you write the keywords field from the variable.

                      Bill
                      Bill Hanigsberg

                      Comment


                        #12
                        RE: Bug? Fields moving fr tabbed panel

                        Didn't know about the xdialog... just took a quick look at the Learning Xdialog book and page 30 seems to show an example of just what you are talking about.

                        Took a quick look into the docs but didn't find the max key length yet.

                        Thanks,
                        Hasan

                        Comment


                          #13
                          RE: Bug? Fields moving fr tabbed panel

                          Hasan,

                          I threw together and *extremely* crude example using action scripting which gives a rough idea of how to go about it.

                          To try the code, create a new script and paste the code into it. You can run the code from the code editor without saving the script. Or you can give the code a name, save it and run it from the control panel.

                          Meanwhile I may have stumbled across the cause of your interface problem. You have linked the keywords table as a child of a set and are also using it as a lookup for the same field.

                          Lose the set. You do not need keywords as a child in a set to utilize it as a lookup source.

                          Bill


                          ---example follows---

                          'Create an XDialog dialog box to prompt for parameters.
                          DIM SHARED vKeywords as C
                          DIM SHARED varC_result as C
                          auto_list_vKeywords = table.external_record_content_get("keywords","Keyword","","")

                          temp_count = w_count(auto_list_vKeywords,crlf())
                          DIM a_vKeywords[temp_count] as c
                          a_vKeywords.initialize(auto_list_vKeywords)
                          heading_string = "header"
                          footer_string = "footer"
                          ok_button_label = "&OK"
                          cancel_button_label = "&Cancel"
                          varC_result = ui_dlg_box("Choose keywords",
                          {endregion};
                          %dlg%)

                          'Displays a message box (style:'OK Button', image: 'Information symbol', id: 'msg01').
                          DIM SHARED msg01_result as N
                          DIM SHARED msg01_OK_Button as L
                          msg01_OK_Button = .F.

                          title_var = "User input"
                          'Message is an expression. Need to evaluate the expression in the context of the current form.
                          message_text_var = a5_eval_expression("=\"User chose \"+Var->vKeywords")
                          msg01_result=ui_msg_box(title_var,message_text_var,UI_OK+ UI_FIRST_BUTTON_DEFAULT+ UI_INFORMATION_SYMBOL)
                          'Test to see which button on the message box was pressed....
                          SELECT
                          CASE msg01_result = UI_OK_SELECTED
                          msg01_OK_Button= .t.
                          END SELECT

                          Bill Hanigsberg

                          Comment


                            #14
                            RE: Bug? Fields moving fr tabbed panel

                            Thanks... I'll try your code.

                            I'm planning to build a master/detail form for the user to maintain contact_types and keywords... won't the set be needed for that?

                            Hasan

                            Comment


                              #15
                              RE: Bug? Fields moving fr tabbed panel

                              Hasan,

                              Not necessarily but it depends on how you want to use it. In general you do not need to link tables to use them as lookups. Keeping this in mind leads to simpler more robust applications. I think you could generate you lookup combinations dynamically.

                              Bill
                              Bill Hanigsberg

                              Comment

                              Working...
                              X