https://bugs.kde.org/show_bug.cgi?id=397891
Bug ID: 397891
Summary: KGeography doesn’t handle images with transparency
Product: kgeography
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: aa...@kde.org
Reporter: k...@huftis.org
CC: lauran...@free.fr
Target Milestone: ---
Created attachment 114616
--> https://bugs.kde.org/attachment.cgi?id=114616&action=edit
Updated map file for Norway (with transparent background)
KGeography doesn’t handle images with transparency correctly. It looks like the
colour of transparent areas aren’t properly recognised.
I’ll attach an example image. This is an updated version of the map for
‘Norway’. The only difference is that the background colour (220,220,220) is
marked as transparent (but it’s still saved as a colour).
How to reproduce:
1. Note that the norway.kgml has a definition for ‘Not Norway’, defined as the
colour (220,220,220), the same colour used as the (transparent) background
colour in the attached image file.
2. Note that the tools/colorchecker.py scripts reports ‘The map is correctly
formed’ when run on the ‘norway.gml’ when the existing ‘norway.png’ is replaced
by the attached file. (If I change the background colour to a *different*
colour, the tool complains, so it seems to work fine.)
3. Note that KGeography correctly loads the image, and shows it with a
transparent background (which looks *much better* than the grey rectangle of
the existing map file).
4. Click on the background of the map to get the following error message:
You have found a bug in a map. Please contact the
author and tell the /usr/share/kgeography//norway.kgm
map has nothing associated to color 220,220,220.
So it looks like KGeography *sees* the colour as 220,220,220, the colour
defined in the .kgm file. But at the same time it doesn’t *handle* it like a
normal 220,220,220 colour.
--
You are receiving this mail because:
You are watching all bug changes.
