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 do I stack windows in a required order

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

    How do I stack windows in a required order

    My Xdialog has a button to call a Browse. When the Browse is displayed it is under the xdialog window, how can I make it display on top of the Xdialog?

    example:
    Code:
    dim global dlg_title as c = "Example"
    ui_modeless_dlg_box(dlg_title,<<%dlg%
    {region1}
    (%B=T;T=Show Historic Browse;O={J=C,C}{C=Yellow}{F=Bahnschrift,10,B}{B=Light Blue}Historic%vOpt:Historic!HistoricBrowseEvent){sp=2}
    (%B=T;T=Close Dialog;O={J=C,C}{C=Yellow}{F=Bahnschrift,10,B}{B=Red}Close%vOpt:Close!CloseDialogEvent);
    {endregion1};
    %dlg%,<<%code%
    if a_dlg_button = "HistoricBrowseEvent" then
    varP_Historical_Logging = :Form.view("Historical_Logging","Dialog")
    varP_Historical_Logging.zorder("top")
    a_dlg_button = ""
    end if
    if a_dlg_button = "CloseDialogEvent" then
    ui_modeless_dlg_close(dlg_title)
    a_dlg_button = ""
    end if
    %code%)
    I am assuming I have to use .zorder somewhere, but where?
    --
    Support your local Search and Rescue Unit, Get Lost!

    www.westrowops.co.uk

    #2
    Graham, I took your code and put it in a script. I had to build a table of some data and created a form to display that data.
    The form contained some fields and an embedded browse.

    When I press the Historic button, the form opens on top of the xdialog.

    My only issue is the the Historic button works only once and I have to close the xdialog and rerun the script to view the form a second time.

    Ron
    Alpha 5 Version 11
    AA Build 2999, Build 4269, Current Build
    DBF's and MySql
    Desktop, Web on the Desktop and WEB

    Ron Anusiewicz

    Comment


      #3
      Build the browse within an xdialog using the option under the browse in design mode - browse - advanced Create Xdialog with embedded Browse
      Attached Files
      Al Buchholz
      Bookwood Systems, LTD
      Weekly QReportBuilder Webinars Thursday 1 pm CST

      Occam's Razor - KISS
      Normalize till it hurts - De-normalize till it works.
      Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
      When we triage a problem it is much easier to read sample systems than to read a mind.
      "Make it as simple as possible, but not simpler."
      Albert Einstein

      http://www.iadn.com/images/media/iadn_member.png

      Comment


        #4
        thanks Al,

        will digest and learn, just what I was looking for (in the Example above and others). That sort of thing doesnt jump out at you in the documentation. :)
        --
        Support your local Search and Rescue Unit, Get Lost!

        www.westrowops.co.uk

        Comment


          #5
          I have tried 'Last_Button as C = FORM.DIALOG( ) and it works well.

          here my sample for event on your codes
          Code:
          if a_dlg_button = "HistoricBrowseEvent" then
          ' varP_Historical_Logging = :Form.view("Historical_Logging","Dialog")
          ' varP_Historical_Logging.zorder("top")
          
          '**create the Global function. call that fuction to open a form from xdlg
          
          'Open the layout_type showing just the records that satisfy the filter
          'Last_Button as C = FORM.DIALOG( Form_Name as C [, Window_Name as C [, Filter as C, [ Order as C [, QueryFlags as C [, Horiz_Position as C [, Vert_Position as C [, ShowNewRecord as L ]]]]]]] )
          'queryFlags -- Optional. Sort instructions. "U" = Unique "D" = Descending
          
          'form condition
          vClose_flag = .f.
          query.order=""
          query.filter = ""
          
          if query.order="" then
          query.order = "recno()"
          end if
          'replace variables in the filter with their actual values
          if query.filter = "" then
          query.filter = ".t."
          end if
          query.filter = convert_expression(query.filter,"VE")
          vLastBttn = form.dialog("sample"," ",query.filter,query.order,"u","center","center")
          
          'close form
          msgbox("test",vLastBttn)
          If vLastBttn = "bttn_close" then 'it is close button and Make sure the property(Object) name of button is "bttn_close"
          vClose_flag = .T. 'form is still remained as open without close at here,
          end if
          '** end global function
          
          
          a_dlg_button = ""
          end if

          Comment


            #6
            Graham,

            I had a similar issue when running a report from a modeless xDialog. The report would run but it would open up behind the xDialog. I’d have to drag the xDialog off to the side to see the report. I’ve been living with this for years. While looking at you issue, I stumbled across some functions I’ve never seen before. Sys_id_hide() and sys_id_show(). This has solved my problem . Now when I click on the report button on the xDialog, the xDialog is hidden and the report is now on top of everything on the screen. When I close the report, the rest of the code runs which then shows my xDialog.

            Thank you for your help.

            Ron

            Code:
            vTitle = "Enter/Change Corrective Actions"
            
            ELSEif a_dlg_button = "view_report" THEN
            if alltrim(vcHeadTransno) = "" then
            msgbox("Oops","Please Select an Open Work Order",UI_ATTENTION_SYMBOL+UI_OK)
            else
            sys_id_hide(vTitle) 'hide this xDialog*********************
            query.filter = "transno = " + s_quote(vcHeadTransno)
            query.order = "transno"
            query.filter = convert_expression(query.filter,"VE")
            :Report.Preview("CA",query.filter,query.order)
            sys_id_show(vTitle) 'show this xDialog********************
            end if
            
            a_dlg_button = ""
            
            ELSEif a_dlg_button = "PrintSqwK" THEN
            Alpha 5 Version 11
            AA Build 2999, Build 4269, Current Build
            DBF's and MySql
            Desktop, Web on the Desktop and WEB

            Ron Anusiewicz

            Comment

            Working...
            X