Wayne,
When I put a new custom library into a directory such as /tmp I am unable to
write to it, and trip up on it in the commented out code in the attached patch.
This seems to be since line 280 of libedit.cpp is returning a filename without a
path. The path portion is empty, and therefore fn.IsDirWriteable( "junk.lib" )
flunks.
For some reason you are not getting a full path. I may have defined the library
to use a relative path when I added it. That could be the difference.
The attached patch is for illustrative purposes only, and is not a fix of any
kind.
Sorry I did not have more time to dig deeper, but you are more familiar with
this code.
Dick
=== modified file 'eeschema/libedit.cpp'
--- eeschema/libedit.cpp 2011-08-12 17:43:16 +0000
+++ eeschema/libedit.cpp 2011-08-16 15:28:06 +0000
@@ -285,6 +285,8 @@
return;
}
+#if 0 // if a library is put into /tmp with relative path, this code does not work since there is no path for some reason.
+
// Verify the user has write privileges before attempting to save the library file.
if( !fn.IsDirWritable() )
{
@@ -293,6 +295,7 @@
GetChars( fn.GetFullPath() ) ) );
return;
}
+#endif
bool success = m_library->Save( fn.GetFullPath(), true );
_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
