From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24698 invoked by alias); 26 Sep 2004 16:43:38 -0000 Mailing-List: contact xconq7-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: xconq7-owner@sources.redhat.com Received: (qmail 24683 invoked from network); 26 Sep 2004 16:43:37 -0000 Received: from unknown (HELO s-hertogenbosch.execulink.net) (199.166.6.44) by sourceware.org with SMTP; 26 Sep 2004 16:43:37 -0000 Received: from diamond.ansuz.sooke.bc.ca (ppp103.ac2.56k.execulink.com [209.213.229.103]) by s-hertogenbosch.execulink.net (8.11.6/8.11.6) with ESMTP id i8QGha119055 for ; Sun, 26 Sep 2004 12:43:36 -0400 Received: from localhost (mskala@localhost) by diamond.ansuz.sooke.bc.ca (8.10.2/8.10.2) with ESMTP id i8QGdkT23781 for ; Sun, 26 Sep 2004 12:39:47 -0400 Date: Sun, 26 Sep 2004 16:52:00 -0000 From: mskala@ansuz.sooke.bc.ca To: xconq7@sources.redhat.com Subject: What does the "image_name" field in the Area structure do? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2004/txt/msg01251.txt.bz2 I wonder if the present discussion of using an image for the map may have already been visited. It appears that there is an "image_name" property associated with each "area", and the read and write code will load and save it in GDL files, but it doesn't seem to be referenced anywhere else. -- Matthew Skala mskala@ansuz.sooke.bc.ca Embrace and defend. http://ansuz.sooke.bc.ca/