http://bugs.winehq.org/show_bug.cgi?id=19254
Summary: Fractal Mapper: some symbols disappear over bitmap backgrounds Product: Wine Version: 1.1.23 Platform: PC URL: http://www.nbos.com/products/mapper/mapper.htm OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: goeran@uddeborg.se
Certain combinations of symbols and backgrounds fail. It appears to happen to the ones called "battlemap" in Fractal Mapper. It can be reproduced with the free trial version (http://www.nbos.com/nox/index.php?action=1001&id=144) and the instructions below assume the defaults in that installation. But the problem is not limited to the trial version, it does also happen to the latest 8.10f version of Fractal Mapper.
1. Install Fractal Mapper according to my instructions in the AppDB (http://appdb.winehq.org/objectManager.php?sClass=version&iId=10813)
2. Start Fractal Mapper.
3. Select "Rectangle" in the "Standard tools" in the top left.
4. Select "Battlemap" as "Fill Style" in the top right. The default desert fill is fine.
5. Draw a large rectangle on the map. It gets the desert fill.
6. Select the chessboard from the "Mapping Symbols" in the lower left.
7. Click-move-release a rectangle over the desert area.
The last step should show the chessboard, but it doesn't.
To illustrate that this has to do with the background, one can
8. Select the "Pointer" in the Standard tools".
9. Click in the large sandy rectangle. (But not where you put the chessboard in it.)
10. Select "Solid Fill" in the "Fill Style".
11. Click "Apply"
The chessboard now appears.
To illustrate that this also depends on what kind of symbol is choosen, one can instead
8. Select "Standard Fantasy Symbols" in the "Mapping Symbols" area.
9. Click on the sea monster.
10. Draw an area in the sandy rectangle.
The sea monster (desert monster?) DOES appear.
http://bugs.winehq.org/show_bug.cgi?id=19254
--- Comment #1 from Göran Uddeborg goeran@uddeborg.se 2009-11-24 06:03:11 --- Philip Killough noted that if you change the display quality (in the "map" menu) from the default "fast" to "good", this problem goes away. Good as a workaround, and maybe also an aid in debugging?
http://bugs.winehq.org/show_bug.cgi?id=19254
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download
https://bugs.winehq.org/show_bug.cgi?id=19254
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME
--- Comment #2 from Bruno Jesus 00cpxxx@gmail.com --- I can't reproduce this in wine 1.1.44 nor 1.7.32, I don't have 1.1.23 to test, since so much time has passed I'll resolve it as worksforme as it could not be reproduced now.
https://bugs.winehq.org/show_bug.cgi?id=19254
Göran Uddeborg goeran@uddeborg.se changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #3 from Göran Uddeborg goeran@uddeborg.se --- I tried again using my full version and wine 1.7.16 I currently have installed. The problem is gone in this combination too. I guess it has been fixed in the meantime.