You are viewing limited content. For full access, please sign in.

Question

Question

WebLink The Image annotation may not be displayed on the document image (45051).

asked on April 27, 2015
 
 

I noticed this listed in an older known issue for Weblink 8.2.2 -

https://support.laserfiche.com/KB/1013209

 

I'm still experiencing the issue in Weblink 9.  (Not that it was claimed to have been fixed, I just didn't see it listed in the known issues of Weblink 9.)

 

Issue: I'm unable to see image annotations in WebLink or WebAccess but can see them in the client. Text annotations show through just fine. When downloading to PDF through WebLink, image annotations do not appear either.

 

Can anyone confirm if this remains a known issue or if a workaround exists?

 

 

Thanks,

Carl

 
0 0

Answer

SELECTED ANSWER
replied on April 29, 2015

No, you should be able to use an ordinary JPEG or PNG image exactly as-is for BitmapAnnotation.ImageData. Please make sure you set the BitmapAnnotation.Size property to the correct value, though.

0 0

Replies

replied on April 28, 2015

Are the images bitonal (also known as black-and--white, or one bit per pixel / 1-BPP) ? When exporting images as a bitonal format (such as TIFF Group 4 Fax), image annotations may become difficult to read because its pixel values are converted into either black or white, as these bitonal image formats do not support intermediate shades of gray values.

1 0
replied on April 28, 2015

Please open a support case with your Laserfiche reseller and provide a copy of the document as well as the image that you're adding as an annotation. I tested in Laserfiche 9.2.1 and WebLink 9 and I am able to add an image annotation, view it in both the Client and WebLink, and also export as a PDF (from the Client) and generate a PDF (from WebLink) and have the image annotation display just fine.

I imported the SAMPLE 1.tif file from C:\Program Files (x86)\Laserfiche\Client into the repository. I then added the following PNG as an image attachment.

Here is what the document looks like in the Client and in WebLink:

Here is what the generated PDF from WebLink looks like:

And attached below is the exported PDF from the Client.

SAMPLE 1.pdf (171.7 KB)
1 0
replied on April 27, 2015

When using the thick client to Export the laserfiche image to a PDF and instructed to include all annotations, it also drops the image annotations.

 

Text annotations are exported with the document just fine.

 

Am I using an unsupported image type? What would be vieable in the client but not from WebAccess, WebLink, or pass through in an export?

0 0
replied on April 28, 2015

They are not 1-BPP so I'll adjust and if that doesn't resolve I'll open a case.

 


Thank you guys for the guidance! I'll update the thread with the results.

0 0
replied on April 29, 2015

Laserfiche must have a conversion process when going from client to web and if the image is easily converted to a bitonal, it shows up, otherwise there may be some difficulty.

 

All images converted to bitonal worked just fine. Even making jpgs not pure bitonal but modified to be "closer" to bitonal by touching up the images, also made it work.

 

Thanks!

replied on April 29, 2015

I should have been more clear in my example and after some testing I've found the 1-BPP information very valuable and it resolved some of the issue.

 

However, when I use the SDK to apply the BitMap Annotation, the problem persists where it's only viewable within the thick client, and not on the web or export. If I manually apply the image annotation (using the same source image) there is no problem.

 

Is there a conversion on the bytes I need to do before setting the BitmapAnnotation.ImageData property?

0 0
SELECTED ANSWER
replied on April 29, 2015

No, you should be able to use an ordinary JPEG or PNG image exactly as-is for BitmapAnnotation.ImageData. Please make sure you set the BitmapAnnotation.Size property to the correct value, though.

0 0
replied on May 4, 2015

This was exactly it. If I didn't set the bitmap size, the bitmap annotation was only visible from the thick client. After setting the size, it worked in all situations.

 

Thank you!

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.