Test Request: Part Design Workflow
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
Be nice to others! Respect the FreeCAD code of conduct!
Re: Test Request: Part Design Workflow
Ok, I'm getting the hang of the basics.
My impressions
My impressions
Need help? Feel free to ask, but please read the guidelines first
Re: Test Request: Part Design Workflow
When i start FreeCAD, I am put in the Start workbench and in the "model view" there is nothing.
Pressing the new document icon populates the "model view" with unamed model.
Now when switching to Part design the "Combo view" switches to "Task view" (offering me to create a body).
Without creating this body when I switsh back to "Model view" it has been populated automatically with a Part containing a Origin and a "Main body".
To me it seams a bit to automatic
-the auto switching of the "Combo box"
-automatic creation of Objects when entering the Part Design workbench.
If the automatic creation of Objects when entering the Part Design workbench was removed, the switching of the "Combo box" would again make sense, because the only obvious choice is to create a new part.
Pressing the new document icon populates the "model view" with unamed model.
Now when switching to Part design the "Combo view" switches to "Task view" (offering me to create a body).
Without creating this body when I switsh back to "Model view" it has been populated automatically with a Part containing a Origin and a "Main body".
To me it seams a bit to automatic
-the auto switching of the "Combo box"
-automatic creation of Objects when entering the Part Design workbench.
If the automatic creation of Objects when entering the Part Design workbench was removed, the switching of the "Combo box" would again make sense, because the only obvious choice is to create a new part.
Need help? Feel free to ask, but please read the guidelines first
Re: Test Request: Part Design Workflow
When creating additive or subtractive parts I have these requests/observations:
1. Make the placement dependent upon the current sensible selection when pushing create button. If a face is selected the part should automatically be placed on that face. Additive parts should by default be put flush on the face and be placed outside the face. Subtractive parts should by default be embedded within the part of the face with nothing protruding out from the face (protruding from any other face of the part is OK).
2. When creating additive or subtractive parts, the newly created part to be linked to mouse movement like in part:move, and be restricted to whatever faces, lines or points are selected before or afterwords in "Coordinate system parameters". This movement to be linked to the placement offset spin indicators in the "Coordinate system parameters".
3. The offset spin indicators in the "Coordinate system parameters" to have x,y,z indication.
EDIT
4. Would it be possible to toggle a additive part to become subtractive.?
5. Is there a possibility in the current implementation to in the future, have mixed additive and subtractive parts.
example : Placing a bolt on a part face would be both, Part of bolt cutting out and the head sticking out?
6. Is there a possibility in the current implementation to in the future, have custom additive or subtractive parts added to these menus?
1. Make the placement dependent upon the current sensible selection when pushing create button. If a face is selected the part should automatically be placed on that face. Additive parts should by default be put flush on the face and be placed outside the face. Subtractive parts should by default be embedded within the part of the face with nothing protruding out from the face (protruding from any other face of the part is OK).
2. When creating additive or subtractive parts, the newly created part to be linked to mouse movement like in part:move, and be restricted to whatever faces, lines or points are selected before or afterwords in "Coordinate system parameters". This movement to be linked to the placement offset spin indicators in the "Coordinate system parameters".
3. The offset spin indicators in the "Coordinate system parameters" to have x,y,z indication.
EDIT
4. Would it be possible to toggle a additive part to become subtractive.?
5. Is there a possibility in the current implementation to in the future, have mixed additive and subtractive parts.
example : Placing a bolt on a part face would be both, Part of bolt cutting out and the head sticking out?
6. Is there a possibility in the current implementation to in the future, have custom additive or subtractive parts added to these menus?
Need help? Feel free to ask, but please read the guidelines first
Re: Test Request: Part Design Workflow
First five minute impressions:
Partially unrelated to new PartDesign issue #0002061 will probably need to be fixed now as PartDesign and Sketcher WB are separated in new PartDesign WB. Therefore toolbar persistence is not possible anymore compared to current PartDesign WB and that will brake work flow substantially compared to current PartDesign WB work flow.
- Boolean Tooltip: boies -> bodies
- No Active Body Pop-Up: Insert active Body object in the EMPTY document automatically instead of Pop-Up.
- Insert new body feature -> Expand everything in Tree View -> Select All -> Delete -> Change to another WB in WB switcher and back -> Crash.
- Additive/subtractive primitive difference is not clear at first glance. After testing it OK one adds one subtracts.
Partially unrelated to new PartDesign issue #0002061 will probably need to be fixed now as PartDesign and Sketcher WB are separated in new PartDesign WB. Therefore toolbar persistence is not possible anymore compared to current PartDesign WB and that will brake work flow substantially compared to current PartDesign WB work flow.
Re: Test Request: Part Design Workflow
Win Builds available here:NewPartDesign
Due to C++11 these build will not work on XP. In addition Visual Studio 2013 Redistributable Package is required for these builds on both x64 and x86.
Due to C++11 these build will not work on XP. In addition Visual Studio 2013 Redistributable Package is required for these builds on both x64 and x86.
"fight the good fight"
Re: Test Request: Part Design Workflow
I opened existing .fcstd file in new PartDesign WB and edited one sketch and after i exited the sketch.
One big Pop-Up telling me something and two smaller pop-ups each telling me something else! After i closed all mentioned pop-ups FreeCAD crashed. At least the big Pop-Up has the option to "never show it again".
Opening existing .fcstd file should be detected at open operation. User should choose if it wants to convert the document to new format or not.
If yes offer save dialogue to preserve original file and do the conversion. Beyond that it's up to the user to check the conversion in the Tree View and no more pop-ups should be issued.
One big Pop-Up telling me something and two smaller pop-ups each telling me something else! After i closed all mentioned pop-ups FreeCAD crashed. At least the big Pop-Up has the option to "never show it again".
Opening existing .fcstd file should be detected at open operation. User should choose if it wants to convert the document to new format or not.
If yes offer save dialogue to preserve original file and do the conversion. Beyond that it's up to the user to check the conversion in the Tree View and no more pop-ups should be issued.
- DeepSOIC
- Veteran
- Posts: 7896
- Joined: Fri Aug 29, 2014 12:45 am
- Location: used to be Saint-Petersburg, Russia
Re: Test Request: Part Design Workflow
sgrogan, thanks for the build
I need a project to test it..
So far, I got one bug:
If I edit a primitive with invalid coordinate system references (invalid in a sense that the combination is not accepted), and erase one of the textboxes of the links, I can't cancel the dialog (I click Cancel, but nothing happens). Yet OK works, while it shouldn't, probably...
I need a project to test it..
So far, I got one bug:
If I edit a primitive with invalid coordinate system references (invalid in a sense that the combination is not accepted), and erase one of the textboxes of the links, I can't cancel the dialog (I click Cancel, but nothing happens). Yet OK works, while it shouldn't, probably...
Re: Test Request: Part Design Workflow
triplus wrote: Opening existing .fcstd file should be detected at open operation. User should choose if it wants to convert the document to new format or not.
ickby wrote:Hello
Please note that the transformation is not yet done, therefore this is known and should be considered:
*Documents done with any other versions may not be loaded or at least wont be transformed to the new part design structure
*Part tools don't recognize the active part object
*documents saved now may not be editable in future versions
"fight the good fight"
Re: Test Request: Part Design Workflow
Crash report here.
Start a new FreeCAD document,
Click the "Create A New Part Feature" tool,
Delete it and everything in the Part folder too (Origin, Planes, Axes, Mainbody),
Select the "Create A New Body Feature" tool,
= crash:
Start a new FreeCAD document,
Click the "Create A New Part Feature" tool,
Delete it and everything in the Part folder too (Origin, Planes, Axes, Mainbody),
Select the "Create A New Body Feature" tool,
= crash:
Code: Select all
[New Thread 0xad573b40 (LWP 6820)]
[New Thread 0xacbffb40 (LWP 6821)]
[New Thread 0xabcd2b40 (LWP 6822)]
[New Thread 0xab4d1b40 (LWP 6823)]
[New Thread 0xaacd0b40 (LWP 6824)]
[Thread 0xaacd0b40 (LWP 6824) exited]
File format not supported: (...Snip... Path to FreeCAD executable here)
[Thread 0xab4d1b40 (LWP 6823) exited]
Program received signal SIGSEGV, Segmentation fault.
__strlen_sse2_bsf () at ../sysdeps/i386/i686/multiarch/strlen-sse2-bsf.S:50
50 ../sysdeps/i386/i686/multiarch/strlen-sse2-bsf.S: No such file or directory.
(gdb)
Re: Test Request: Part Design Workflow
Confirmed - Same here.bejant wrote:Crash report here.
Start a new FreeCAD document,
Click the "Create A New Part Feature" tool,
Delete it and everything in the Part folder too (Origin, Planes, Axes, Mainbody),
Select the "Create A New Body Feature" tool,
= crash:
Code: Select all
[New Thread 0xad573b40 (LWP 6820)] [New Thread 0xacbffb40 (LWP 6821)] [New Thread 0xabcd2b40 (LWP 6822)] [New Thread 0xab4d1b40 (LWP 6823)] [New Thread 0xaacd0b40 (LWP 6824)] [Thread 0xaacd0b40 (LWP 6824) exited] File format not supported: (...Snip... Path to FreeCAD executable here) [Thread 0xab4d1b40 (LWP 6823) exited] Program received signal SIGSEGV, Segmentation fault. __strlen_sse2_bsf () at ../sysdeps/i386/i686/multiarch/strlen-sse2-bsf.S:50 50 ../sysdeps/i386/i686/multiarch/strlen-sse2-bsf.S: No such file or directory. (gdb)
Code: Select all
Program received signal SIGSEGV, Segmentation fault.
strlen () at ../sysdeps/x86_64/strlen.S:106
106 ../sysdeps/x86_64/strlen.S: No such file or directory.
(gdb) bt
#0 strlen () at ../sysdeps/x86_64/strlen.S:106
#1 0x00007fffcb308638 in CmdPartDesignBody::activated(int) () from /home/mark/Build/Assembly/Mod/PartDesign/PartDesignGui.so
#2 0x00007ffff7584ffc in Gui::Command::invoke(int) () from /home/mark/Build/Assembly/lib/libFreeCADGui.so
#3 0x00007ffff541187a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4 0x00007ffff5b6da62 in QAction::triggered(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#5 0x00007ffff5415c1e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6 0x00007ffff5b6f4f2 in QAction::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#7 0x00007ffff5b73e2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#8 0x00007ffff5b7a4a0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#9 0x00007ffff754240f in Gui::GUIApplication::notify(QObject*, QEvent*) () from /home/mark/Build/Assembly/lib/libFreeCADGui.so
#10 0x00007ffff53fd4dd in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#11 0x00007ffff5400b3d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#12 0x00007ffff542af83 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#13 0x00007fffee978e04 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007fffee979048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007fffee9790ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007ffff542a7a1 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#17 0x00007ffff5c15bb6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#18 0x00007ffff53fc0af in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#19 0x00007ffff53fc3a5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#20 0x00007ffff5401b79 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#21 0x00007ffff753a089 in Gui::Application::runApplication() () from /home/mark/Build/Assembly/lib/libFreeCADGui.so
#22 0x00000000004040a0 in main ()
OS: Ubuntu 14.04.2 LTS
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.16.5452 (Git)
Branch: assemblyMergeMaster1
Hash: 5a424e5f1437c7a5970a50dc1229065000a9d7ab
Python version: 2.7.6
Qt version: 4.8.6
Coin version: 4.0.0a
OCC version: 6.8.0.oce-0.17
This post made with 0.0% Micro$oft products - GOT LINUX?