Your C++ is not so bad as you always claim@wmayer: thanks for being so patient with my C++ and for all the tests, coments and hints!
I'll try out soon.I'm not going to make any changes unless there is something wrong, broken or missing.
Your C++ is not so bad as you always claim@wmayer: thanks for being so patient with my C++ and for all the tests, coments and hints!
I'll try out soon.I'm not going to make any changes unless there is something wrong, broken or missing.
Thanks, but that's not true I'm mostly copying code from other parts of FreeCAD or stackoverflow Then a quick variable rename, adding a random const or static and I can claim I did all the codingwmayer wrote:Your C++ is not so bad as you always claim@wmayer: thanks for being so patient with my C++ and for all the tests, coments and hints!
I'll try out soon.I'm not going to make any changes unless there is something wrong, broken or missing.
Code: Select all
#include "PreCompiled.h"
#ifndef _PreComp_
# include <QListWidget>
# include <QDragMoveEvent>
# include <QString>
#endif
Code: Select all
QListWidgetCustom::QListWidgetCustom(QWidget * parent)
: QListWidget(parent)
{
}
Code: Select all
#ifndef QLISTWIDGETCUSTOM_HPP
#define QLISTWIDGETCUSTOM_HPP
...
Interesting thougth.. In freecad it actually doesn't bother me much (I guess I'm used to it), but it is true that I don't like that in other apps (openoffice for example, or draftsight). But also having huge, complex preferences systems where you loose hours trying to find your option is also annoying. Anyway, this deserves some thinking...ian.rees wrote: To me, the distinction between what is a Preference and what is a Customization is not clear.
The idea doing it this way was taken from MS's Visual Studio.To me, the distinction between what is a Preference and what is a Customization is not clear.