+ fixed background logo for Win and Linux
+ improved QToolBar handle for different icon sizes (selectable by user inside Preferences)
+ tweaked editable fields inside QToolBar in order to work for all icon sizes (selectable by user inside Preferences)
+ fixed Ubuntu problem that caused a blank line inside up/down buttons of QSpinBox and similar
+ tweaked Python Editor color for Light theme
+ fixed buttons margin/padding inside Task tab
+ tweaked color for checked QPushButtons inside Draft WB for better user experience
QString::fromAscii() is obsolete in Qt5. Replace it with fromLatin1().
QString::toAscii() is obsolete in Qt5. Replace it with toLatin1().
QChar::fromAscii() is obsolete in Qt5. Replace it with fromLatin1().
This change is Qt4/Qt5 neutral.
This function accepts 2 optional arguments: a string (ex. "Draft")
and an integer (ex. 2). If given, the preferences dialog will open at
the third tab of the Draft group, if existing.
=====================================================
What?
Extension of the CommandMacro constructor to take an additional optional argument to indicate that the macro
is located in the system-wide directory, and shall be executed accordingly.
===============================================
What?
Implementation of triplus' idea of making user-specific and system-specific macros
having a different list in different tabs.
Fixing of a bug related to the previous "separator".
Suggested terminology.
=====================================================
What?
It was suggested that the macros should be moved to AppUserHome/Macro
http://forum.freecadweb.org/viewtopic.php?f=10&t=13433
Solution:
The solution is backwards compatible in the sense that if you have a running
configuration, updating should not change anything.
For new installations the macro directory will default to AppUserHome/Macro. However
this would break all the installation scripts (probably also ME's plugin manager).
Conflicts:
src/Mod/Path/Gui/AppPathGuiPy.cpp
===============================================
What?
Support for executing system-wide macros in /usr/lib/freecad/Macro
http://forum.freecadweb.org/viewtopic.php?f=10&t=13433
Why?
To allow to package macros and install them system-wide so that they are available to all users.
