Hello,

I made some changes to a PV750 program, and when I tried to create the downloadable file, I got this message at the end:

The confguration was not created sucessfully due to the following error:
Bitmap region is already locked.

My only choice was to close.

What does this mean and how do I fix it?

Thanks,
Phil

This happens whether I create Full Install or Changed.

Can you tell me what you have tried already. I assume a close and reopen of PowerVision didn't take care of it?

If not, shoot me your config and the specific version your using and I will take a look. Most likely there is an image that's invalid or something similar.

I've had this error come up in the past using PowerVision 2.3 and manipulating the parameters of Widgets. I haven't a clue what sets it off. I have been unsuccessful to back track my steps to correct the error. I used to quit w/o saving and restart with my last backup, but recently I did try a save, close PowerVision, restart PowerVision, open the file, and run "Create" again ... it worked w/o generating that error.

What does that error mean exactly?

The error is simply us catching an error in Windows Image processing system. There are a number of possible causes including a malformed image from an external image editor. Another possibility is an image being manipulated/created at the same time the graphics drawing subsystem is trying to simulate the pages in Page Designer. Since a 750 uses images for each font glyph (character) there is a LOT of image construction during the create process which makes this even more likely. One way to make this less likely to occur is to not be on the page designer when doing a create....but the better answer is for us to figure out how to reproduce it and fix it.

Regardless of the cause, it is a bug related to how we are catching the invalid image or preventing two processes from accessing the image at the same time. This is likely something thats corrected/impossible to see when working in 2.6 and/or with a 700 which doesn't use pixel mapped data but instead uses a set of vector drawing commands to describe fonts and most other drawn components.

I will log this to look into for a 2.3 patch and hopefully we can find something in there. If anyone has managed to recreate it, that would help for sure.

I did not find what did it. I ended up reverting to an earlier version.

thanks,
Phil