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

print screen

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

    print screen

    I am working on an idea. Here is my goal:

    Push the "Print Screen' button
    capture the complete current screen
    save that to a constant bitmap name
    print a report using that bitmap

    Using alpha's
    ui_bitmap_create_from_screen("test", 0, 0, 8.5, 11)

    I should now have a full copy of the screen.

    If I always copy the current screen to the same file as a bitmap, I could design a report, with the option to 'display printer options on print'

    This would let me have the user use the 'print screen' or other special key to capture the current screen and send it to the report, whch would give the user the normal windows 'printer select' dialog and then print a bitmap of the current screen.

    but where I'm getting stuck is saving and then printing

    I need to be able to save it to file to the same name each time - thus setting up the report.

    ui_bitmap_create_from_screen("test", 0, 0, 8.5, 11)
    this apparently creates the bitmap in memory only, and I haven't been able to figure out how to save it to disk - apparently you have to deal with it as a blob - but I can't find a 'file save blob-to-bitmap' method

    Push the "Print Screen' button
    capture the complete current screen
    save that to a constant bitmap name
    print a report using that bitmap






    Cole Custom Programming - Terrell, Texas
    972 524 8714
    [email protected]

    ____________________
    "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

    #2
    RE: print screen

    Martin

    In bitmap functions - bitmap_to_png() is the one that I'd recommend.

    See attached image.
    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


      #3
      RE: print screen

      Al, from the documentation, I think you have to already have a bitmap image on a disk - what I can't figure out is how to save the "image" to a disk

      ui_bitmap_create_from_screen("test", 0, 0, 8, 6)

      how can I save that to disk as a bitmap image - that's what I can't figure out. Or, for that matter, if I have a table with a bitmap/field, how to save it to that record.


      f=file_create("c:\alpha\aadfw\test.bmp", file_rw_exclusive)
      'this creates a blank bitmap
      ui_bitmap_create_from_screen("test", 0, 0, 8, 6)
      '?how to get this image to the bitmap I created above?
      Cole Custom Programming - Terrell, Texas
      972 524 8714
      [email protected]

      ____________________
      "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

      Comment


        #4
        RE: print screen

        Martin

        The key is that the image is a blob variable. This should work

        xbasic_wait_for_idle()
        ui_bitmap_create_from_screen("test", 0, 0, 8, 6)
        imageb = ui_bitmap_save("test")
        f=file_create("c:\alpha\aadfw\test.bmp", file_rw_exclusive)
        f.writeb(imageb)
        f.close()

        ui_bitmap_drop(imageb)

        The Calendar & Toolbox addin has a built in function to save a screenshot of an xdialog which uses code similar to this.

        Jerry

        Comment


          #5
          RE: print screen

          Hello Martin,

          Try this:

          ui_bitmap_create_from_screen("test", 0, 0, 8, 6)

          vBlob = ui_bitmap_save("test")
          file.From_blob("c:\test.bmp",vBlob)


          Jim

          Comment


            #6
            RE: print screen

            Jerry, I got error 1499 with your code.

            Here is the code I ended up with that works like a champ!!

            ui_bitmap_create_from_screen("test", 0, 0, 8, 6) '800 X 600
            vBlob = ui_bitmap_save("test")
            file.From_blob("c:\alpha\aadfw\test.bmp",vBlob)
            t=table.open("cscreen")
            t.change_begin()
            t.cscreen=vblob
            t.change_end(.t.)
            form.view("cscreen")
            report.preview("cscreen")
            end


            cscreen is a 1 field, 1 record table with a bitmap as type
            the report is "best fit"

            I can use the same code on any form, and it replaces the table record each time, so the report is always on the last image.

            I'll have to modify for the network, but thanks a million - as always, I had skirted around the correct code 10 times, but missed the part of vblob in the below line

            file.From_blob("c:\alpha\aadfw\test.bmp",vBlob)
            Cole Custom Programming - Terrell, Texas
            972 524 8714
            [email protected]

            ____________________
            "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

            Comment


              #7
              RE: print screen

              actually,

              'file.From_blob("c:\alpha\aadfw\test.bmp",vBlob)

              is unnecessary
              Cole Custom Programming - Terrell, Texas
              972 524 8714
              [email protected]

              ____________________
              "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

              Comment


                #8
                Re: print screen

                Hi Martin,

                I am trying to use your print screen routine in a script, print_form, called by a form button. Here is the script I am using:

                'Print form
                ui_bitmap_create_from_screen("test", 0, 0, 8.5, 6.5)
                vBlob = ui_bitmap_save("test")
                t=table.open("cscreen")
                t.change_begin()
                t.cscreen=vblob
                t.change_end(.t.)
                form.view("cscreen")
                report.preview("cscreen")
                end

                The error that I am getting when executing it is attached.

                I created a table cscreen with one record named Screen_Image as a bmp, best fit.

                Then I created a form cscreen with the field Screen_Image as 8.5 x 6.5 in, best fit, and imported an image to have something in the file.

                Lastly, I created a form cscreen with nothing on it but the field Screen_Image at 7.5 x 5.7" w. best fit, reducing the size to fit the page. It shows the one record.

                Then I ran the script from a button on the 8.5" x 6.5" form that I want to capture and got the error.

                Any suggestions about what I am doing wrong would be much appreciated.
                Richard

                Comment


                  #9
                  Re: print screen

                  Richard,

                  According to your description you have a table called cscreen with a field called Screen_Image. Therefore your code should be:
                  Code:
                  t=table.open("cscreen")
                  t.change_begin()
                  t.[B][COLOR="Red"]Screen_Image[/COLOR][/B]=vblob
                  t.change_end(.t.)
                  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


                    #10
                    Re: print screen

                    Thanks Tim,

                    It often takes a friend to point out the painfully obvious... :o

                    Much appreciated.
                    Richard

                    Comment


                      #11
                      Re: print screen

                      My pleasure.
                      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

                      Working...
                      X