The use of state variables would help with multi-user preference problems, but it does little to help with the needs of users who must prepare several illustrations based all or in part on a single set of vector data. For that case we need a separate set of drawing attributes for each illustration. Furthermore, if the illustration is to remain dynamic (changing when the underlying vector data are changed) then those sets of drawing attributes must be maintained as an optional part of the vector attributes database. That means (for instance) that if a vector object is deleted from the database, then it’s drawing attributes need to be removed from the set of attributes used by any illustration that uses the object. Perhaps that requirement is too stringent for GRASS. >, If each person has there own set of state variables, then this problem will only arise if two or more people are working on one illustration. In fact, there isn’t any software anywhere – and never will be – that can settle a disagreement between two people working on one illustration. That’s what supervisors are for. >, Mulitple access problems aren’t unique to the vector drawing attributes. I think that needs to be addressed in a different thread. GRASS already supports the use of different drawing attributes for raster maps. For instance, we have reclass maps, regions, 3dviews and color tables that are supported and maintained by the system and are quickly manipulated to prepare different images. If a raster file is removed, then the database elements associated with it are also removed. That support is perhaps not as developed as it could be. I would like to see at least that much support provided for vector drawing attributes. >, I agree, but remember there are several respondents that didn’t want to support drawing attributes at all. I was simply allowing the system to operate with default attributes for those people who don’t want anything else. >, That isn’t quite true. Drawing attributes are used every time a vector object is displayed. Nothing is drawn without attributes, you can’t draw a line even on the most basic of monitors without a line width, a line style and a line color. You can’t draw a point without a size, a color and a style. There is also no clear distinction between attributes needed for vector analysis and attributes needed for presentation, though clearly one would want to manipulate more attributes for illustration than for analysis. >, I agree completely, but don’t forget that somewhere in the morasse of code there are inherent defaults. Currently, lines are displayed in white, as solid lines with a single-bit width. Points have a similar set of defaults. >, The global default attributes would be stored in the system. User preferences (alterations of the defaults) could be stored in the user’s space. The tables of attributes prepared by the user for each illustration can be kept as separate tables within the vector database, much as 3dviews are stored now for raster illustrations. >, I think we agree on the use of state variables. Roger Miller Lee Wilson and Associates —————————————- If you want to unsubscribe from GRASS Development Team mailing list write to: Source.