On Mar 23, 2006, at 2:43 AM, Robin Bowes wrote:
> Vadim Kurland =E2=9C=88 wrote:
>> On Mar 21, 2006, at 10:21 AM, Robin Bowes wrote:
>>> I've tried creating a library file in which to keep all my common
>>> objects, i.e. custom stuff that is shared across multiple fwb files.
>>> I did this be creating a new fwb project file then exporting the =20=
>>> user library immediately into a file called Common.fwl. I closed the
>>> project file and added the library using Edit|Preferences|=20
>>> Libraries. I
>>> renamed the new library object to Common (it was called "User") and
>>> changed the background colour.
>> libraries loaded via Preferences/Libraries can not be edited. If you
>> wish to edit such library, you just open it using File/Open
> Would it be possible to make these libraries writable in the same way
> that .fwb files are? I'd like to be able to copy objects from an
> existing configuration into the library for use in other files.
library file is writable if you open it using File/Open. When library =20=
is loaded "in background", it is merged with the file you are working =20=
with and do not exist as a separate entity. This is because any file, =20=
not just library file, may have object library with the same ID and =20
name and these libraries are merged together when all files are opened.
Once library file is created, it becomes somewhat complicated to move =20=
object into it from other files. You can recreate an object in such =20
library file manually, or merge it in. For the latter you need to =20
open original file where the object resides, create temporary object =20
library and move object to it, then export temporary library to a =20
file. Then you open your library file and merge temporary library =20
into it using File/Import library. This is inconvenient and I should =20
look into ways to improve this operation, but this is the way it is =20