I have noticed that there is no way to pick which catalog file is used when one creates a new dg catalog entry via the wall panel.
What is the suggested approach? Its likely that if users are creating additional wall types they will want to be going into the project catalog - can I control this, perhaps a config variable for the behaviour of the creation of a new entry would be an idea, and then a pull down that allows you to create at project or site level.
On a seperate note with the exception of the above flaw, the dg wall palette is starting to look pretty good in functional terms, is there a plan to bring the other palettes in line with this. At the moment the range of behaviour across the placement tools is bewildering.
AECOSIM 08.11.09.225
The recommended method is to copy the 'x-Template | Project_Wall' using the 'Save a Copy of Catalog Item' icon. This will write the new wall to the project dataset.
Thats a nice feature of the US dataset.
Its a non-existent feature of the GB dataset...
Good guide though so basically what you are saying is that copying from a particular file will honor the file source.
Thanks!
You can also create the DG catalog entry from DG Catalog Editor. When you create a new catalog item you will have the option to select the XML file that will store the information. Chose one from the project dataset location. I don't have the GB dataset in front of me but it should be in a similar location as the US one. Looks like this image:
Robert,
Mark is correct in that the best/easiest method for creating project specific catalog items is to copy the project templates. I am not involved in the GB Dataset so I will have to take your word that there are not templates in the GB Project Template. I would recommend creating some project templates in an XML stored in your template project datagroupcatalogs directory. For the US Dataset I included project templates for most (if not all) architectural and structural catalogs.
HTH,
Travis
The issue is that the gb dataset has a project specific catalog, but no entries so its difficult to know its there.
There is the wider issue that the intetion of the location specific datasets is that it shouldn't be editable, project datasets are the only ones that should be editable, not least because a new localised dataset should over right the exiting and delete any changes.
Would you consider adding something like a catalog writable config variable? That would allow writability to be controlled by configuration.
Better still a resource writable config variable that could prevent any resource file being tampered with.
Robert