Bitmap shows mirrored / flipped over with flashing background

Has anyone seen a bitmap shown as a mirrored version of original bitmap with a flashing background?

This is weird and I have done nothing different than I did in other watchfaces where I used the same bitmap. It is a bluetooth icon and is a png file.

I merely copied the png to my new watchface project from another watchface where is works.

I suspect it is something to do with the size of the *.prg file. It is 64kb in size.

Is it the compiler that alters the bitmap resource as a way to warn you you are over the limit?

The memory usage in the simulator shows 33kb out of 64kb.

What is causing this?

Former Member over 10 years ago

Generally when you see bitmaps with funny colors it means the image was compiled for the wrong device. Are you seeing this on the device/simulator? How are you deploying/running the prg file?

HermoT over 10 years ago

Generally when you see bitmaps with funny colors it means the image was compiled for the wrong device. Are you seeing this on the device/simulator? How are you deploying/running the prg file?

Thanks, it was that indeed!

Simulator showed it fine, it was just on my actual watch where the problem was.

But what eclipse does that causes the confusion, is the following:

If you build for specific device, and you specify the output path to be the root of the bin folder, then it replaces the device specific prg file with another one.
It always seem to build 2 versions of the prg file, but overwrites the device specific one.
I only managed after creating a subfolder in bin, like bin/920xt, and specified that as the output path.
Now I get a prg file in both bin and bin/920xt, where the two files differ in size.

Hope you can prevent this confusion by having a better way to prevent accidental overwriting of device specific prg files.
Like a naming convention of some sort? watchface_920xt.prg etc

Former Member over 10 years ago

As a general rule I would avoid using the bin folder (or a sub folder of the bin folder) of your project when building for a specific device. You might try updating your plug-in. A change was made recently that prevented changes to the bin folder from triggering an automatic build which I'm guessing is the problem you were running into.