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

Image file reference field problem on reports.

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

  • Image file reference field problem on reports.

    Why does Alpha5 v5 render photos different between a form and a report even though the image file reference field settings are the same? This presents a big quality problem of cross hatching with some photos (ones that the origional is wider than tall), both in display (print preview) and print out of the report.

    I want to know how I can solve this problem or work around it if someone has already solved this.

    I have posted 4 messages total and attached one screen capture file illistrating the problems to each for viewing purposes.

    Explanation:

    The origional photo named OrigionalOFA2888.jpg is 1.62" w x 1.24"h x 150 pixels per inch (resolution). This translates into 243 pixels x 186 pixels x 150 pixels per inch (resolution). and is attached to this message.

    I have a form with an image file reference field on it. The field size is 2.5" x 2.5". In the setup for the field on the form the Display Mode is: Absolute. The screen capture photo named AbsoluteImageForm is of the above sized photo displayed in the image file reference field on the form and looks normal.

    The report has an image file reference field on it. The field size is 2.5" x 2.5". I have two screen captures, one of the photo with the field Display mode set as Absolute, and the other set as Stretch for the display mode.

    The image named AbsoluteImageReport is captured from the report with the image file reference field set to absolute. You can see it is way smaller than either it's origional size or the absolute size displayed on the form.

    The image named BestFitImageReport is captured from the same report, with the image file reference field Display mode set to Best Fit. As the capture shows there are black lines cross hatching the photo. This is not acceptable in on screen display and photos with crosshatching also print out with the black lines (cross hatch) showing.

    Making the origional image larger or smaller does not improve the display in a report. In fact it makes it worse with more cross hatching.

    Please see the other 3 posts for the additional files. If it is better that I post all the files in a zip file I can do that.

    Thanks,

    Phil DeGruy


  • #2
    RE: Image file reference field problem on reports.

    This post contains the origional file as it is displayed in the image file reference field of the form.

    The field size is 2.5" x 2.5". In the setup for the field on the form the Display Mode is: Absolute. The screen capture photo is named AbsoluteImageForm is of the origional sized photo displayed in the image file reference field on the form and looks normal.


    Phil DeGruy

    Comment


    • #3
      RE: Image file reference field problem on reports.

      The image named AbsoluteImageReport attached is captured from the report with the image file reference field set to absolute. You can see it is way smaller than either it's origional size or the absolute size displayed on the form.

      Why is this??


      Phil DeGruy

      Comment


      • #4
        RE: Image file reference field problem on reports.

        The image named BestFitImageReport is captured from the same report, with the image file reference field Display mode set to Best Fit. As the capture shows there are black lines cross hatching the photo. This is not acceptable in on screen display and photos with crosshatching also print out with the black lines (cross hatch) showing.

        I think the photo is cross hatched because the report for some reason sees the origional photo as something smaller than a postage stamp and is stretching it to fit.

        BTW, stretch causes the image aspect ratio to go wacky, when I tried that setting.

        Phil DeGruy

        Comment


        • #5
          RE: Image file reference field problem on reports.

          Forgot:

          Making the origional image larger up to 2.5" wide x aspect less than 2.5" (don't remember what the number was now) or smaller (less than 1.2" wide and keeping the aspect ratio)does not improve the display in a report. In fact it makes it worse with more cross hatching or does not show all the photo when looking at the image on the form.

          Thanks,

          Phil DeGruy
          chowchow@ticon.net

          Comment


          • #6
            RE: Image file reference field problem on reports.

            The absolute mode prints one image pixel for each display/print pixel. Since printers are much higher resolution than monitors, the image is smaller.

            Alpha Five uses the native Windows image scaling algorithms for stretch and best fit. Unfortunately, these are rather poor quality algorithms. We are looking into finding a better solution.

            If you want to solve the problem with some programming, you could produce a scaled image for the report using a third party product, such as offered by XnView.

            Comment


            • #7
              RE: Image file reference field problem on reports.

              Thanks for the explanation as to the different sizes So once again windows strikes it's ugly head.


              It would be very nice if Alpha did handle photos much better. I have noticed many posts wanting to store photos of inventory objects, photos of people, etc.

              I discussed this with the person who is doing the photo scanning and we are going to see if we can come up with something that will work without having to do to much rework.

              I will take a look at XnView's software offerings, but I'm not sure if I can handle the programing required to make things work.


              Thanks,

              Phil DeGruy

              Comment

              Working...
              X