Search found 656 matches
- Tue Dec 03, 2019 3:10 am
- Forum: Open discussion
- Topic: Dedicated Spreadsheet Workbench Maintainer/Devs needed
- Replies: 29
- Views: 5493
Re: Dedicated Spreadsheet Workbench Maintainer/Devs needed
3696 also seems to be a duplicate of the "Expression can't contain space" error. I've revived an old thread here to try to spark some discussion around the best way to address this issue. In the meantime, I'll keep chugging away at Spreadsheet-specific issues. Moving on to my second list! ...
- Tue Dec 03, 2019 3:08 am
- Forum: Open discussion
- Topic: Linked constraints don't work with spaces.
- Replies: 12
- Views: 2356
Re: Linked constraints don't work with spaces.
there is no need to allow this in expressions as well. In my opinion the only possible bug is that expressions accept spaces... I am reviving this old thread due to the work I'm currently working on trying to make some small improvements to the Spreadsheet module. See here . One of the bugs listed ...
- Tue Dec 03, 2019 1:25 am
- Forum: Open discussion
- Topic: Dedicated Spreadsheet Workbench Maintainer/Devs needed
- Replies: 29
- Views: 5493
Re: Dedicated Spreadsheet Workbench Maintainer/Devs needed
Update: After spending some time learning how to duplicate the issue described in 3272 , I've determined that the root cause of this issue appears to be in the App::ExpressionParser::parse function - it does not seem to support spaces in the name of a constraint (or, strictly speaking, in the "...
- Mon Dec 02, 2019 10:52 pm
- Forum: Install / Compile
- Topic: Ticket #4145 - build failure with assembly module enabled
- Replies: 15
- Views: 3819
Re: Ticket #4145 - build failure with assembly module enabled
Ok, if it's kept as a reference I would say it must at least compile successfully I agree with this: if the user is able to select a portion of the code base in the build system, then it should compile. If the only reason to keep the code is for reference, then we should remove the BUILD_ASSEMBLY c...
- Mon Dec 02, 2019 8:01 pm
- Forum: Open discussion
- Topic: Bug #5750: Failed to parse expression occurs when referencing an alias in an external spreadsheet document
- Replies: 6
- Views: 3140
Re: Bug #3272: Failed to parse expression occurs when referencing an alias in an external spreadsheet document
I have found the steps necessary to reproduce the error - it seems that this is somehow connected to using a named constraint. In other words, the following results in no error Create new document switch to Spreadsheet workbench Save document and give it a name, i.e. "MasterSpreadsheet.fcstd&qu...
- Mon Dec 02, 2019 4:38 pm
- Forum: Help on using FreeCAD
- Topic: OpenInventor Mouse Model on Laptop
- Replies: 4
- Views: 552
Re: OpenInventor Mouse Model on Laptop
If it worked before, you can try to reset the configuration by moving (for later resetore) the config file. Then change nothing but the mouse model. Tried this, still have the same behaviour. What camera type do you have activated? Perspective or orthographic? Orthographic camera view. Preferance /...
- Mon Dec 02, 2019 3:48 am
- Forum: Open discussion
- Topic: Bug #5750: Failed to parse expression occurs when referencing an alias in an external spreadsheet document
- Replies: 6
- Views: 3140
Re: Bug #3272: Failed to parse expression occurs when referencing an alias in an external spreadsheet document
ping @bgoodr (or anyone) - can you provided a step-by-step on how to reproduce the issue from "scratch"? I can confirm the error using the provided tarball, however I've attempted a few times to set up the same scenario and can't reproduce the error. Edit: Attached are the files I've crea...
- Mon Dec 02, 2019 3:31 am
- Forum: Help on using FreeCAD
- Topic: OpenInventor Mouse Model on Laptop
- Replies: 4
- Views: 552
OpenInventor Mouse Model on Laptop
I am using a Lenovo Thinkpad, T410. My middle mouse button works fine in general, however within FreeCAD, the OpenInventor mouse model seems to get a bit confused. The following GIF shows what happens when I press+hold the middle-mouse button, and then move my mouse (trackball) up/down. Notice that ...
- Mon Dec 02, 2019 1:55 am
- Forum: Help on using FreeCAD
- Topic: Bug: Crash in Python Console
- Replies: 21
- Views: 1732
Re: Bug: Crash in Python Console
I was able to reproduce this using a release build. Here are the specs of the build: OS: Gentoo/Linux Word size of OS: 64-bit Word size of FreeCAD: 64-bit Version: 0.19.18817 (Git) Build type: Release Branch: master Hash: 6d79dbea432e4c7b53b0b94667a9930b7d5b5104 Python version: 3.6.5 Qt version: 5.1...
- Sun Dec 01, 2019 1:09 pm
- Forum: Help on using FreeCAD
- Topic: Bug: Crash in Python Console
- Replies: 21
- Views: 1732
Re: Bug: Crash in Python Console
The problem is that maybe this only happens in debug build... Can you reproduce if you compile a release build ? I was thinking the same. I'll need to recompile in order to test, I'll let you know. Why is this showing an obsolete version of 0.19 ? I mostly have "dirty" freecad executables...