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

XDialog: how to set dropdown height?

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

  • XDialog: how to set dropdown height?

    I am trying to use XDialog for data entry. XDialog is new to me, so I started with an Action Script, converted it to XBasic, and tarted it up. It works, but the drop-down list for Name (produced using keylist_build) is only about 5.5 rows high (screenshot atatched). 10 lines or so would be nice.

    I have gone through the help files, and have tried several variations of adding %.70,10 in various places, but clearly not in the right place. Please can anyone help ?

    Here's the main part of the XDialog:

    Code:
    DIM SHARED vxdEntryDate as D
    DIM SHARED vxdDescription as C
    DIM SHARED vxdName as C
    DIM SHARED vxdChqName as C
    DIM SHARED vxdAmount as C
    dim shared temp as n
    DIM SHARED vxdPaidIn as C
    DIM SHARED vxdAccount as C
    DIM SHARED vxdCategory as C
    DIM SHARED varC_result as C
    DELETE expression_result
    expression_result = eval("date()",form_name)
    vxdEntryDate = convert_type(expression_result,"D")
    
    vxdPaidIn = "No"
    
    auto_list_vxdDescription = table.external_record_content_get("e_income_descriptions","Description","Order","")
    temp_count = w_count(auto_list_vxdDescription,crlf())
    DELETE a_vxdDescription
    DIM a_vxdDescription[temp_count] as c
    a_vxdDescription.initialize(auto_list_vxdDescription)
    
    auto_list_vxdAccount = table.external_record_content_get("e_income_accounts","Account","Order","")
    temp_count = w_count(auto_list_vxdAccount,crlf())
    DELETE a_vxdAccount
    DIM a_vxdAccount[temp_count] as c
    a_vxdAccount.initialize(auto_list_vxdAccount)
    
    auto_list_vxdCategory = table.external_record_content_get("e_income_categories","Category","Order","")
    temp_count = w_count(auto_list_vxdCategory,crlf())
    DELETE a_vxdCategory
    DIM a_vxdCategory[temp_count] as c
    a_vxdCategory.initialize(auto_list_vxdCategory)
    
    ok_button_label = "&OK"
    cancel_button_label = "&Cancel"
    edit_button_label = "&Edit client record"
    
    DIM vxdName_rl_def as C 
    vxdName_rl_def = "k=clients,{keylist_build(\"H=.05,1:30[Name],2:34[Cheque name],3:60[Short notes]\",''+Calcflname,left(''+Calcflname,26),left(''+Cheque_name,30),left(''+Shortnotes,70))}{}"
    
    ' It's a new income record, so blank out all fields except those with a default
    vxdDescription = ""
    vxdName = ""
    vxdChqName = ""
    vxdAmount = ""
    vxdAccount = ""
    vxdCategory = ""
    
    'Turn off the hourglass cursor.
    hourglass_cursor(.f.)
    
    varC_result = ui_dlg_box("Income record",<<%dlg%
    {font=Arial,9}
    {ysize=2}
    {region}
    {tabstops}
    Entry date:| [%DATE;P=popup.calendar(dtoc(vxdEntryDate));I=popup.calendar%.17vxdEntryDate!vxdEntryDate_*];
    Description:| [%v%.41vxdDescription^+a_vxdDescription];
    Name:| [%@vxdName_rl_def%.45vxdName!change]|{endtab}{notabstops}<20=edit_button_label!EDIT>;
    {endtab}{tabstops}
    Cheque name:| [.45vxdChqName];
    Amount:| [%*n%.12vxdAmount!amtchange];
    {region}Paid in:{endregion}|
    {region}(vxdPaidIn:No) 
    (vxdPaidIn:Yes){endregion};
    Account:| [%v%.30vxdAccount^=a_vxdAccount];
    Category:| [%v%.30vxdCategory^=a_vxdCategory];
    {endtab}
    {endregion};
    {ysize=1}
    {line=1,0};
    {region}
    <15=ok_button_label!OK> <15=cancel_button_label!CANCEL>
    {endregion}
    %dlg%,<<%code%
    if left(a_dlg_button,13) = "vxdEntryDate_" then 
    	if a_dlg_button = "vxdEntryDate_killfocus" then 
    		vxdEntryDate = ctod(dtoc(vxdEntryDate))
    	end if 
    	a_dlg_button = ""
    end if
    
    ' Each time the Name is changed, look up the cheque name
    if a_dlg_button = "change" then
    ... (and so on)

  • #2
    Re: XDialog: how to set dropdown height?

    My reading says

    Code:
    vxdName_rl_def = "k=clients,{keylist_build(\"H=.05,1:30[Name],2:34[Cheque name],3:60[Short notes]\",''+Calcflname,left(''+Calcflname,26),left(''+Cheque_name,30),left(''+Shortnotes,70))%.70,10}{}"
    But no experience here.
    There can be only one.

    Comment


    • #3
      Re: XDialog: how to set dropdown height?

      change this line to:
      Code:
      Name:| [%@vxdName_rl_def%.45,10vxdName!change]|{endtab}{notabstops}<20=edit_button_label!EDIT>;

      Comment


      • #4
        Re: XDialog: how to set dropdown height?

        Wow, that was quick ! Thanks Stan and G for looking at this.

        Still not there, though ... Stan's change greys out the Name control (no drop-down available), and G's change turns the Name control itself into an edit box 10 lines deep. When you click it to drop down the list, the list itself is still 5.5 lines deep.

        (Screenshots attached)

        Comment


        • #5
          Re: XDialog: how to set dropdown height?

          A sample database for testing would go a long way. You say "the drop-down list" but there is more than one way to obtain a drop down list.
          There can be only one.

          Comment


          • #6
            Re: XDialog: how to set dropdown height?

            Are you trying to modify name? or Cheque name?

            Comment


            • #7
              Re: XDialog: how to set dropdown height?

              Apologies for not being clear: I'm trying to modify (increase the height of) the list which gets dropped down when you click the drop-down button on the Name field.

              I've attached a sample DB (I hope). To recreate the problem:
              • go into Forms, and open the only form there (Entries_Income)
              • then click the "New" button at the bottom left, to bring up the XDialog which I'm having trouble with
              • now click the drop-down button in the Name field.

              This displays a list with three columns (Name, Cheque name and Short notes). The list is only 5.5 rows deep, and this is what I'm trying to increase.

              Please do say if I'm still not making sense, or if there is a problem with the sample DB - I do appreciate your help. I've got to go to an appointment now, so will check in later. Many thanks.

              Comment


              • #8
                Re: XDialog: how to set dropdown height?

                Alpha doesn't like me modifying your example in V8 but I don't see the capability to vertically expand the dropdown list. The width and height of the undropped list can easily be changed. No help there.
                There can be only one.

                Comment


                • #9
                  Re: XDialog: how to set dropdown height?

                  OK Stan - thanks for having a look. I'm not sure if it can be done.

                  *edit* Looking at an old V6 post, it seems that the height of the dropdown list is related to the font size, but I can't see how to fool it into thinking that it is using a larger font size than it really is. Might give up on this one.
                  Last edited by Bonbon; 04-19-2011, 07:22 PM.

                  Comment

                  Working...
                  X