I have two suggestions.
First off I would like to see a copy like item/assembly functionality for the database.
There is several assemblies I have created that have upwards of over a dozen components in them.
While only a few items within the assembly may differentiate it with another making assembly creation rather tedious. The ablilty to copy the whole assembly and make minor tweaks to it would greatly speed up the building process.
Another would be some kind of masking feature that allows you to hide items that exist in the database solely as part of an assembly. This could reduce the number of items you have to search through when looking for specific items or assemblies.
Regarding the database
- Gennaro Vellotti
- Posts: 51
- Joined: Wed Oct 14, 2009 3:28 pm
- Company: Netafim Australia & New Zealand
- City / Town: Adelaide
- Location: Adelaide, Australia
- Contact:
Re: Regarding the database
A temporary measure to get around this is to open a new project in Irricad, select just that assembly and put it on your screen. Save the project, then open the internal database of that project rename just the assembly to your new assembly, then save it. Then merge this internal database in your main database, is relatively quick and shouldn't duplicat any of the components. You can then delete/add to suit the new assembly.MikeM wrote:I have two suggestions.
First off I would like to see a copy like item/assembly functionality for the database.
There is several assemblies I have created that have upwards of over a dozen components in them.
While only a few items within the assembly may differentiate it with another making assembly creation rather tedious. The ablilty to copy the whole assembly and make minor tweaks to it would greatly speed up the building process.
Gennaro Vellotti
Irrigation Engineer Lead
Netafim Australia/NZ
+61 419 362 845
Irrigation Engineer Lead
Netafim Australia/NZ
+61 419 362 845
Re: Regarding the database
Gennaro - That helps immensly, thanks for the tip!