Hi I don't think Qt stylesheet supports even half of this #style-9::-webkit-scrollbar-track { -webkit-box-shadow: inset 0 0 6px rgba(0,0,0,0.3); background-color: #F5F5F5; } so you best bet is to dig into https://doc.qt.io/qt-5/stylesheet-examples.html#customizing-qscrollbar and see how close you can get it.

Well, huh. I thought I tried that one with the bigger project before, but it does work with the test program here, so that must have been something else. Thank you for your assistance.

@Burke212 change setup(); CWC = new customWidgetClass(); to CWC = new customWidgetClass(); setup(); hopefully you did initialize CWC as nullptr, otherwise that would have crashed in release mode 10/10 times.

Finaly I have finished my little example! Previous version have been really buggy in items move. So I have to subclass from QAbstractItemModel. Many thanks to @Patou355 with his solution. NB I haven't deal with mousePressEvent() yet.

Why do you have your plugins and application all in the same project ?

@Valveware said in Promoting to custom widget in QtDesigner '*.hpp' no such file or directory [cmake]: file(GLOB_RECURSE QT_MOC RELATIVE ${CMAKE_CURRENT_SOURCE_DIR} FOLLOW_SYMLINKS include/dashboard/*.hpp) Ok that looks like it would indeed moc your cameraframe.hpp.. So that's probably not the issue. Can you share the build log from gcc? And also the ui_main_window.h file as well as ui_cameraframe.h?

@mghqt i assume CWidget class is the main widget (window)? How do you compose/layout the form items? Are you using sub-widgets containers? Anyways you should do like you did for pos4 if you want to map a child to a parent. QPoint childPos=ui->label_2->mapTo(this, ui->label_2->pos());

Perfect. Thank you very much. It works perfect. So that other people, if they have the same problem here have the solution. It's very simple and I did not fall for something so simple. In the properties where I assign the texts and icons we call a method that modifies the margins. Only that. For example: #import PyQt5 or PySide (To the taste of the client) class Test(QDialog): def __init__(self, parent: QDialog = None): super().__init__(parent) self.__row_Text = None @property def row_Text(self) -> str: return self.__row_Text @row_Text.setter def row_Text(self, value: str): self.__row_Text = value self.updateFancyBackground() self.repaint() def updateFancyBackground(self): # I liked the name Fancy Background if self.__row_Text is not None: margins = self.layout().contentsMargins() margins.setTop(24) self.layout().setContentsMargins(margins) def paintEvent(self, event: QPaintEvent): # Your code for height = 24 pass Many thanks to "SGaist" and "mrjj", for giving me the idea to solve it.

@Ilan My question is what method of the widget does the Qt designer use for showing If you mean Qt Designer showing your custom widget in the toolbox along default widgets (i.e. QLabel, QLineEdit, etc.) I guess you may need to create a plugin for Qt Designer from your custom widget. Qt Designer used a plugin based approach, see here.

@Sh1gs Just as a note. There is no difference adding widgets in code or adding via Designer. The setupUI() as seen in mainwindow ctor creates the Designer widgets as code. So the only true difference is handwritten versus generated from UI file. Also adding via Designer, gives easier translations as the translate function is generated for the user.

@VRonin After some headache days I found the problem. The FilterWindow widget had set wrong the parent in children widgets, so, the right way would be : void FilterWindow::setUi(std::string tittle) { Frame = new QFrame(this); //Here it must be this, to set the widget itself as the parent Frame->setObjectName(QStringLiteral("Frame")); Frame->setFixedWidth(281); Frame->setFixedHeight(89); Frame->setStyleSheet(QLatin1String("QFrame\n" "{\n" " border-style: solid;\n" " border-width: 0px;\n" " border-radius: 4px;\n" " border-color: transparent;\n" "}")); Frame->setFrameShape(QFrame::StyledPanel); Frame->setFrameShadow(QFrame::Raised); Frame->setAttribute(Qt::WA_DeleteOnClose); checkBox = new QCheckBox(Frame); checkBox->setText(tittle.c_str()); checkBox->setObjectName(QStringLiteral("checkBox")); checkBox->setGeometry(QRect(0, 0, 248, 35)); checkBox->setAutoFillBackground(false); checkBox->setStyleSheet(QLatin1String("QCheckBox\n" "{\n" " background-color: rgb(128,139,143);\n" " color: white;\n" " border-radius: 4px;\n" " padding-left: 8px;\n" "}\n" "\n" "QCheckBox::indicator:unchecked {\n" " image: url(:/OptiNanoPro/uchk);\n" "}\n" "\n" "\n" "QCheckBox::indicator:checked {\n" " image: url(:/OptiNanoPro/chk);\n" "}\n" "")); checkBox->setChecked(true); ArrowBtn = new QPushButton(Frame); ArrowBtn->setObjectName(QStringLiteral("ArrowBtn")); ArrowBtn->setGeometry(QRect(246, 0, 36, 35)); ArrowBtn->setAutoFillBackground(true); QIcon icon; icon.addFile(QStringLiteral(":/OptiNanoPro/DownArrwLd"), QSize(), QIcon::Normal, QIcon::Off); ArrowBtn->setIcon(icon); ArrowBtn->setIconSize(QSize(36, 35)); ArrowBtn->setFlat(true); Table = new QTableWidget(Frame); Table->setObjectName(QStringLiteral("Table")); Table->setGeometry(QRect(0, 35, 281, 31)); Table->setStyleSheet(QLatin1String("QTableWidget\n" "{\n" " background-color: white;\n" " border-radius: 0px;\n" "}" "\n" "QCheckBox\n" "{\n" " color: white;\n" " padding-left: 8px;\n" "}\n" "\n" "QCheckBox::indicator:unchecked {\n" " image: url(:/OptiNanoPro/uchk);\n" "}\n" "\n" "QCheckBox::indicator:checked {\n" " image: url(:/OptiNanoPro/chk);\n" "}\n" "")); ResetBtn = new QPushButton(Frame); ResetBtn->setText("Reset"); ResetBtn->setObjectName(QStringLiteral("ResetBtn")); ResetBtn->setGeometry(QRect(0, 66, 169, 23)); ResetBtn->setStyleSheet(QLatin1String("QPushButton\n" "{\n" " background-color: white;\n" " border-width: 1px;\n" " border-style: solid;\n" " border-color: rgb(86,86,84);\n" " border-radius: 3px;\n" " color: rgb(86,86,84);\n" "}")); AplyBtn = new QPushButton(Frame); AplyBtn->setText("Apply"); AplyBtn->setObjectName(QStringLiteral("AplyBtn")); AplyBtn->setGeometry(QRect(169, 66, 111, 23)); AplyBtn->setStyleSheet(QLatin1String("QPushButton\n" "{\n" " background-color: white;\n" " border-width: 1px;\n" " border-style: solid;\n" " border-color: rgb(86,86,84);\n" " border-radius: 3px;\n" " color: rgb(86,86,84);\n" "}")); }

@Sh1gs Just as a note. You can visually design the UI in Designer and then just grab the c++ code. ;) If you look inside the setupUI, there is the code for what u have"drawn"

Hi @Joel-Bodenmann , thank you, I got the point about the item delegate but I see two issues: implement a drag and drop listview because I ended up with empty lines (on the list view) and fields on the widget mapper: https://s32.postimg.org/47yyrq7id/Untitled.png implement a delegate that paint a checkbox with custom pixmap, the input with number and the input with text.

@Prisco I'm glad it worked out. Good luck with your project!

@ghielmetti Hi Normally I do have the .h file in the project folder and point to that in the Promote dialog. Im not sure it will take a full path in the dialog but I never tried :)

Hi, You followed the "simple way" of creating a Designer plugin. For a "real world" approach take a look at this. Short version: you split your plugin code in two: a library which will include your widget(s) the plugin itself That way you have the plugin for designer and you can link your application to the library which will not have any dependency on designer related code. Hope it helps

@raven-worx Hello, Thanks for the code, but I know how to do the scheduling. I actually went with QPointer<QObject> since the QObject might be deleted while waiting in the event loop. Like this: bool AgDial::eventFilter(QObject * object, QEvent * event) { switch (event->type()) { case QEvent::ChildAdded: QMetaObject::invokeMethod(this, "scheduleChildAdd", Qt::QueuedConnection, Q_ARG(QPointer<QObject>, QPointer<QObject>(reinterpret_cast<QChildEvent *>(event)->child()))); break; case QEvent::ChildRemoved: d()->detachAction(reinterpret_cast<QChildEvent *>(event)->child()); break; } return QStackedWidget::eventFilter(object, event); } Thanks for taking the time though! Kind regards.

Hi @maximo, did you have success with the MacNativeWidget and didi it reach your requirements.

Hi, That generally means that you are trying to use a plugin built with a version of Qt (e.g. 5.5) with an application built with a different version (e.g. 5.4) So check what version of Qt was used to build Qt Creator and use it to build your plugin.

@p3c0 Thank you! Works fine.

Hi and welcome to devnet, How are you calling findChildren ?