Nice! I'll have a look at it ASAP.

Nice! what about CTRL+E or SHIFT+E or CTRL+SHIFT+E or alternatively a combination with ALT?

Yes this is also possible but then you have to run the python executable because otherwise freecadcmd interprets the given parameters: python script.py c:/123.stp c:/321.igs import sys # if python cannot find the FreeCAD stuff add the path here sys.path.append("path_to_freecad_module") fil...

You can pass a file (if the type is supported) and FreeCAD loads it but it's not possible to save a file this way. But a much better way is to write a little python script and pass this as parameter. import Part shape=Part.Shape() shape.importStep("file.step") shape.exportIges("file.i...

The repository must be on Launchpad because when trying to define an external repository Launchpad gives you an error.

Edit: For me the git_commit doesn't work either. Here the report https://launchpadlibrarian.net/92810327/buildlog.txt.gz

Here the test build recipe: https://code.launchpad.net/~freecad-mai ... rick-daily

git-commit uses the last 7 characters of the git commit, time is UTC date and time. So we'd get something like 0.13-gitbde6022+20120212093846, from what I understand the timestamp would make sure it'd be considered as the latest, but I'm not sure it's enough for the system to consider it higher tha...

Hi Yorik,

you have to use the method instead. The isEditing() method is almost used when an operation is running that works on more than only one object (e.g. mesh cutting). And AFAIK the setEditing() is not called when using the setEdit() method of the document.

When opening the CMakeLists.txt the first time Qt creator shows a panel where you can pass some parameters to cmake. Enter this in order to have the debug symbols: -DCMAKE_BUILD_TYPE=Debug

BTW, which compile errors did you get?

Apparently there is something not properly setup with your VS installation. I guess when you create a little test application created with the VS wizard you'll get the same error. Besides that you should use VS 2008, not VS 2010 because all the LibPack libraries are built with VS 2008 and won't work...