ImageEn for Delphi and C++ Builder ImageEn for Delphi and C++ Builder

 

ImageEn Forum
Profile    Join    Active Topics    Forum FAQ    Search this forumSearch
Forum membership is Free!  Click Join to sign-up
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 ImageEn Library for Delphi, C++ and .Net
 ImageEn and IEvolution Support Forum
 ImageEnMView Issues with 5.2
 New Topic  Reply to Topic
Author Previous Topic Topic Next Topic  

kandc

29 Posts

Posted - Dec 01 2014 :  12:38:46  Show Profile  Reply
Hi,

I have an ImageEnMView and ImageEnVect working together on one form to perform editing on multipage Tiff files. Essentially, the user opens the file, has the ability to edit one or more pages, adding annotations, before saving the entire tiff back to disk. The ImageEnMView is used for thumbnails and selecting the page, while the ImageEnVect is used to perform annotations.

Because ImageEnMView does not support displaying of annotations, I have had to create two ImageEnMViews, one for display only (call it MDisplay) and the other is a working copy (call it MWorking - nonvisual). Basically, as annotations are made, they are saved back to MWorking as annotations and they are burned to MDisplay so that the annotations will appear on screen. Since MWorking has the official copy of the multipage Tiff, I can still work with the objects. If the page is changed, the current annotations are saved to MWorking and they are burned to MDisplay. When the new page is loaded into Vect, it is loaded from MWorking with the annotations. Visually, this has the effect of displaying annotations on thumbnails.

Problem: My MView does not have a parent, it is created solely for working purposes and I receive random, "control has no parent." The problem goes away if a parent is established. Seems like a bug.

Question: Is there a better way of working with a multipage tiff than using a background copy of MView?

Suggestion: Provide an option in MView that simulates the burning of annotations onto the bitmap for display purposes only so that a separate working copy does not have to be maintained. Others have requested annotations be viewable on MView, this might be a way around the problem?

Thanks,

Kevin

xequte

39141 Posts

Posted - Dec 01 2014 :  19:05:50  Show Profile  Reply
Hi Kevin

1. The issue of an MView not having a parent is resolved in the current beta. Email me for the source.

2. I am investigating a ShowAnnotations property for TImageEnMView.


Nigel
Xequte Software
www.xequte.com
nigel@xequte.com
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
Jump To: