ektemple / glimmr-i7x

Automatically exported from code.google.com/p/glimmr-i7x
4 stars 1 forks source link

Some Automap tiles are missing #25

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Downloaded Full Release 3.2
2. Created a new project
3. Copied all the images from "Glimmr Automap Assets" and "Glimmr Automap 
Tileset Assets" to "Materials/Figures"
4. Added these lines to my source code:

Include Glimmr Automap by Erik Temple.
Include Glimmr Automap Tileset by Erik Temple.
The map-window is a map-display window spawned by the main-window. The position 
is g-placeabove.
The map-canvas is a g-canvas. The associated canvas of the map-window is the 
map-canvas.
The associated canvas of the map-renderer is the map-canvas. The associated 
canvas of a UI-element is the map-canvas.
When play begins:
     follow the opening up the map window rules.

5. Compiled and played it

What is the expected output? What do you see instead?

The canvas window opens as expected, it begins to draw the tilesets. Then 
gnome-inform7 crashes with this error message:

(gnome-inform7:32431): Chimara-WARNING **: load_image_from_file: Error loading 
resource from alternative location "/home/kb/Inform/Projects/GlimmrTest 
Materials/Figures/Automap_Tileset_059.png": Failed to open file 
'/home/kb/Inform/Projects/GlimmrTest 
Materials/Figures/Automap_Tileset_059.png': No such file or directory
zsh: segmentation fault  gnome-inform7

Given, gnome-inform7 should not segfault because of such an error. However the 
error goes away when I do 

cp Materials/Figures/Automap_Tileset_0{58,59}.png

What version of the product are you using? On what operating system?

Release 3.2 on Ubuntu 10.10 in gnome-inform7 (1.2 6.31/6G60)

Please provide any additional information below.

I suppose some of the tiles that are used e.g. in the Example project 
"Automapping the Manse.gblorb" were not included in the release. 

Original issue reported on code.google.com by konstant...@gmail.com on 10 Feb 2011 at 1:56

GoogleCodeExporter commented 9 years ago
This is fixed in release 3.3

Original comment by Ek.Temple@gmail.com on 3 Mar 2011 at 4:01