Note: You must be registered in order to post a reply. To register, click here. Registration is FREE!
T O P I C R E V I E W
Scazon
Posted - 16 May 2007 : 06:44:16 While libnames.txt helps to a certain extent, it would be very useful if multiple library search paths could be included, similar to the system used by compilers. We could then copy our modified libraries to a user folder, and have this searched first, any unlocated elements then being imported from the standard library (if this is next in the list).
This would also prevent updates from squogging our new components incautiously added to standard libraries.
A second, related, request is to give a choice when changing a component's properties- the program often responds that the local version will be used. Could we not have a choice to use the local version, or the newer version, with the warning that it will be used for ALL instances in the design?
1 L A T E S T R E P L I E S (Newest First)
Peter Johnson
Posted - 16 May 2007 : 07:07:02 Thank you for raising these points. The first has been raised before by other users, so it's already in the 'wish list' for version 11 (though that's no absolute guarantee that it will be implemented).
The second has not been requested before, but sounds like a simple enough change! I've passed the request on to the development team.