atomdocs wrote:Hi Shawn, I noticed that too. Sorry that it didn't work out. As Paul says, Capture is a capture tool, not an image editing suite. I have tried to resist that, and make Capture work harder, but it is frustrating when it fails like this. I really don't think it is just down to an intentionally limited scope. Considering some of the really clever stuff that Capture can do, it does some of the basic stuff poorly. I suppose it is a question of development time and resources. In today's fierce market and going up against Adobe, I suppose MadCap wants to focus on their core product. It is commonly said that not many people use Capture. Perhaps they don't use it because of these fail points.
Thanks Tom.
There core product isn't a complete documentation tool. There are times I am really excited about what I can do with Flare but I am beginning to notice, as my documentation becomes more complex, that I am occasionally wondering if I made a mistake by not sticking with Adobe FrameMaker. These thoughts are based on the expanding realization that Flare cannot do many tasks that are basic to FrameMaker.
Anyhow, I need a solution for this image quality mess! But I suspect that it will never get solved until Flare integrates Capture into Flare.
The way I see it, the problem is:
- I resize the images in Capture (in order to keep all the bubbles a consistent size)
- Capture saves a flattened/permanently reduced image in .png format
- The reduced .png is updated in Flare
- The screen captured image can never be expanded to 1:1 without pixalization.
Again, am I the only person using bubbles in screen captures?
