Is it true that some library objects cannot be used in SBuilder? Other programs do not, for example, use the ASO type objects because they are not XML based. Is this also true of SBuilder.
If some objects can never be used in SBuilder perhaps they should be eliminated from the list or "greyed out".
Dick
Valid Library Objects??
Hi,
You are right! However I would like to support the old format! Note that you can edit objects.txt and delete the lines that you know that do not work. objects.txt is an user file. You can your creation objects here. Also note that I have plans to increase the potencial of this part of Sbuilder. The following is from the help file:
You will notice that the file consists of several lines with one line per object. Each line defines 6 parameters separated by "spaces". The first parameter is the 128 bit Identifier of the object. The second parameter is the Type of library object. At the time of writing only Type=1 library objects are supported. Type=1 library objects refer to FS9 only compatible library objects. Type=0 library objects will refer to FS8 library objects. Type=2 objects will refer to macro objects. For Type=2 objects the Identifier parameter (the first parameter in a line) can have a different size. The 3rd and 4th parameters are Width and Length that can be used in defining a FootPrint for precise object positioning. The 5th parameter is the Scale of the object. The 6th parameter is the Name of the object. The name cannot contain any space.
Regards, Luis
You are right! However I would like to support the old format! Note that you can edit objects.txt and delete the lines that you know that do not work. objects.txt is an user file. You can your creation objects here. Also note that I have plans to increase the potencial of this part of Sbuilder. The following is from the help file:
You will notice that the file consists of several lines with one line per object. Each line defines 6 parameters separated by "spaces". The first parameter is the 128 bit Identifier of the object. The second parameter is the Type of library object. At the time of writing only Type=1 library objects are supported. Type=1 library objects refer to FS9 only compatible library objects. Type=0 library objects will refer to FS8 library objects. Type=2 objects will refer to macro objects. For Type=2 objects the Identifier parameter (the first parameter in a line) can have a different size. The 3rd and 4th parameters are Width and Length that can be used in defining a FootPrint for precise object positioning. The 5th parameter is the Scale of the object. The 6th parameter is the Name of the object. The name cannot contain any space.
Regards, Luis