Release of 0.18
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
Be nice to others! Respect the FreeCAD code of conduct!
Re: Release of 0.18
One thing that would be cool, is to always add the file used to generate the splashes to the examples folder... Provided we have the author's permission of course
- wandererfan
- Veteran
- Posts: 6309
- Joined: Tue Nov 06, 2012 5:42 pm
- Contact:
Re: Release of 0.18
"The FreeCAD Community" may not have a legal existence, but "members of the FreeCAD Community" do.Joel_graff wrote: ↑Tue Jan 08, 2019 2:42 pmCode: Select all
Copyright 2019, Juergen Riegel, Werner Mayer, Yorik van Havre and the FreeCAD Community
Re: Release of 0.18
just to add some tips, attached the LO License reference
They added
Anyway I would keep the three main contributors in front of the others like:
They added
...'Copyright by LibreOffice contributors'
Anyway I would keep the three main contributors in front of the others like:
'This product was created by Juergen Riegel, Werner Mayer, Yorik van Havre'
Re: Release of 0.18
Thanxwmayer wrote: ↑Tue Jan 08, 2019 11:50 am git commit 55a4f78ad
This datum feature seems to be pretty useful.
Re: Release of 0.18
Can confirm and thanks.
OK:
- On GitHub browse to the file you would like to Edit.
- Press on the Edit button (creates a Fork and a branch automatically).
- Edit.
- Press on PR button.
- Congratulations, you have just become a FreeCAD developer and a FreeCAD source code contributor.
Re: Release of 0.18
Yea, NormandC, let me know how I can help you with this stuff. I created Developing_FreeCAD_with_GitKraken because working with git makes most sense to me using a GUI.
Alone you go faster. Together we go farther
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
Re: Release of 0.18
This relates to FreeCAD_0.18.15609_Conda_Py3QT5-WinVS2015_x64 build
When I run the unit tests once all the tests pass, when I run it the second time I get this error
OS: Windows 10
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.18.15609 (Git)
Build type: Release
Branch: master
Hash: a14af0f2bd26f980d71be80a799ee48127bc7619
Python version: 3.6.6
Qt version: 5.6.2
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: Slovenian/Slovenia (sl_SI)
When I run the unit tests once all the tests pass, when I run it the second time I get this error
Code: Select all
Traceback (most recent call last):
File "C:\Users\saso\Desktop\FreeCAD_0.18.15609_Conda_Py3QT5-WinVS2015_x64\bin\lib\unittest\case.py", line 59, in testPartExecutor
yield
File "C:\Users\saso\Desktop\FreeCAD_0.18.15609_Conda_Py3QT5-WinVS2015_x64\bin\lib\unittest\case.py", line 605, in run
testMethod()
File "C:\Users\saso\Desktop\FreeCAD_0.18.15609_Conda_Py3QT5-WinVS2015_x64\Mod\Test\Document.py", line 1577, in testDocument
self.failUnless(self.Obs.parameter.pop(0) is self.Doc1)
File "C:\Users\saso\Desktop\FreeCAD_0.18.15609_Conda_Py3QT5-WinVS2015_x64\bin\lib\unittest\case.py", line 1321, in deprecated_func
return original_func(*args, **kwargs)
File "C:\Users\saso\Desktop\FreeCAD_0.18.15609_Conda_Py3QT5-WinVS2015_x64\bin\lib\unittest\case.py", line 682, in assertTrue
raise self.failureException(msg)
AssertionError: False is not true
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.18.15609 (Git)
Build type: Release
Branch: master
Hash: a14af0f2bd26f980d71be80a799ee48127bc7619
Python version: 3.6.6
Qt version: 5.6.2
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: Slovenian/Slovenia (sl_SI)
Re: Release of 0.18
Hi all,
For information, the part-design example in 0.18 in in the 0.16 way of designing, so opening it can lead to misunderstanding for beginners as there is no body and part.
attached the updated version (lighter by the way).
For information, the part-design example in 0.18 in in the 0.16 way of designing, so opening it can lead to misunderstanding for beginners as there is no body and part.
attached the updated version (lighter by the way).
Code: Select all
OS: Debian GNU/Linux buster/sid
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.18.15611 (Git) AppImage
Build type: Release
Branch: master
Hash: 64a94ae0f7c60fc981086fe157150a9c0dca29c6
Python version: 2.7.6
Qt version: 4.8.6
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: French/France (fr_FR)
Re: Release of 0.18
I just noticed that Meshes --> Unwrap Mesh and Unwrap Face are not available in Crowdin for translation...
Yorik, no success in making the FEM menus appear I gather?
Contrary to the cute icon, I was not smiling.
In any case, GitKraken requires signing in through either GitHub or a GitKraken account - which makes it a no-go for me.
Yorik, no success in making the FEM menus appear I gather?
And what if you have more than one file to edit, which was my case?
I know, I recently marked it for translation. I also noticed that you uploaded blasted animated GIFs, and you know my opinion about this image format.
Contrary to the cute icon, I was not smiling.
In any case, GitKraken requires signing in through either GitHub or a GitKraken account - which makes it a no-go for me.
Re: Release of 0.18
The moment I posted the above response and then linked on the page... I knew you'd give me for itNormandC wrote: ↑Sat Jan 12, 2019 9:14 pmI know, I recently marked it for translation. I also noticed that you uploaded blasted animated GIFs, and you know my opinion about this image format.
Contrary to the cute icon, I was not smiling.
In any case, GitKraken requires signing in through either GitHub or a GitKraken account - which makes it a no-go for me.
Alone you go faster. Together we go farther
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs