Great ! Since you have it working now, please mark the thread as solved using the "Topic Tools" button or the three dotted menu beside the answer you deem correct so that other forum users may know a solution has been found :-)

@pauledd You mean the background color "overspill" to right & bottom? I don't know but you might play with border-... or padding-... (I'm thinking margin- does not use background color, but I might be wrong) having a width/transparency/grey....

I found the problem. I was drawing the beats before the lines, so the lines took precedent over the beats since they are siblings. The solution was to either draw the beats last or set the Z value on the beat, not the note.

Hi @tansgumus , Apple is very conservative in allowing developers long term background threats/events. Taken from the Apple docu: Implementing Long-Running Background Tasks For tasks that require more execution time to implement, you must request specific permissions to run them in the background without their being suspended. In iOS, only specific app types are allowed to run in the background: Apps that play audible content to the user while in the background, such as a music player app Apps that keep users informed of their location at all times, such as a navigation app Apps that support Voice over Internet Protocol (VoIP) Newsstand apps that need to download and process new content Apps that receive regular update from external accessories Apps that implement these services must declare the services they support and use system frameworks to implement the relevant aspects of those services. Declaring the services lets the system know which services you use, but in some cases it is the system frameworks that actually prevent your application from being suspended. That said, a navigation app should fall in this category. But as it is, you're bound to do it in OBjective-C but its relative easy to include ObjectiveC code in Qt.

Yeah, that looks ok. I wasn't suggesting to remove the flush permanently, just to see that the system background is drawing when you don't flush. Btw. Keep in mind that the system color can change at any time so if you want to be 100% correct you should either get it every time you render or handle the WM_SYSCOLORCHANGE and WM_THEMECHANGED messages.

@tansgumus said in Button backgound non-existent property!: Component.onCompleted: { // WORKS! // button.background.color = "red" // WRONG background = Rectangle { color: "red" } } Because Component.onCompleted is a javascript function and you can use only js syntax inside it. Rectangle { color: "red" } is QML specific syntax, js doesn't understand it. You can create a component dynamically (see the QML docs) by giving the component as a string to Qt.createQmlObject(). If you use button.background.color = "red" in Component.onCompleted it retains all other properties of the backround; I have found it to be a convenient way to change only one or two properties without messing others. Using other approaches, i.e. defining the whole component either dynamically or declaratively, overwrites everything which may or may not be desirable.

I was always searching at the wrong place. The blue hue wasn't a problem of the style, it was a problem of the icon. Here is the solution: for all icons m_clientIcon.normal.addFile("plugins\\qtTsOverlay\\client.png"); add this m_clientIcon.normal.addFile("plugins\\qtTsOverlay\\client.png", QSize(), QIcon::Selected);

@MarceloGomez The About code works for me using setStyleSheet . setStyleSheet("QMainWindow { background-image: url(:/icon/Icon.jpg); }");

@raven-worx I mean drawing part is quite simple, but there is a stuff QGraphicsPathItem doesn't provide, so I had to implement my own class. I will make some experiments with QGraphicsPathItem later, but for now viewportUpdateMode solves an issue.

Thank you! Just perfect! :D

@vlada Android Visualizer class. But it probably has bug in API level 26.

@VRonin Hi Oh yeah, I didn't think about a .gif ! That will spare me the complication of trying to find a way to make the scene recurrent. Thank you !

I have added these few lines to resemble GIF image as background for QListWidget QPixmap pix = QPixmap::grabWidget(ui->label,20,30,741,481); pix.fill(Qt::transparent); QPalette p; p.setBrush(QPalette::Base,pix); p.base();

@SGaist Argh everything's too confusing. I think I'll just leave it for now haha

Ok, I just realized that I was asking for QPalette::Window of the widget itself, not the application. Nothing wrong with being stupid.

Thank you mrjj ! that was it !

@Orby I finally figured this out. Go into project -> android build options -> Details on build android APK Click create templates, now you can edit that AndroidManifest.xml and set the option to true.

Hi @Pheelbert, if you meant changing the background of dropdown list then you will need to do it in __dropDownStyle private property for now. eg: inside ComboBoxStyle __dropDownStyle: MenuStyle { itemDelegate.label: Text { width:200 height: 80 color: "blue" text: styleData.text } itemDelegate.background: Rectangle { color: styleData.selected ? "darkGray" : "transparent" } } And to add an arrow you can just use an Image inside the background: Rectangle { component.

@Chris-Kawa, you got me wrong i guess, the problem is not stylesheet inheritance, it's about the target widget itself NOT getting the stylesheet, instead that only passing style to children, naming him doesn't affect the result too.