General and Desktop

@hutiien You probably will need to install older VS version or Microsoft Build Tools version which has this old compiler. Keep in mind that you probably will not be able to use latest Qt versions with this compiler.

@jsulm Yep you're right I did miss the obvious Doh! Slap head! painter.setPen(pen) would help a lot!

@JonB Hi, I have added the separator. Its working fine. Thank you everyone for your support.

@hoarylea How did you install Qt? Also, C:\Qt\Tools\QtDesignStudio\qt6_design_studio_reduced_version\lib\Qt6Widgetsd.lib is not the correct lib to link. How did you configure your project?

@Bonnie Understood! thank you for your help!

@Chris-Kawa Is there an effective method for troubleshooting and monitoring memory fragmentation and memory leaks under Windows? How can I judge whether the current status is normal? I hope to receive your guidance

@HowitzerDev Menu bar items have a transparent background by default, so the menu bar will be visible. You can style the items to have opaque background using QMenuBar:item style and that will cover the menu bar background under the items.

Okay I did this in QT Designer and it worked well :) I didn't understand what syntax was usable Thanks for your help @JonB [image: 0291aa8e-5742-4b46-86e7-0624d3ef2f15.png]

@ollarch Yeah, just multiple humans don't work like multiple threads... And we don't Mutex well. :)

@printfne I believe (though not certain) that it is indeed an axes issue. When adding points to an existing series on the chart I think you have to adjust the axes to ensure it is within range to show,. All that matters in my code is the updating of the axes' ranges in addSeriesValues(). What does qDebug() << chart->axes().count() report? I assume the chart must always have some idea of axes and range/scale, else how would it know where to plot anything? If you have some points visible initially, you might also trying adding new points within the range of what is already there instead of beyond it. Maybe you would see such points updated. This question is about not seeing newly added points after the initial display of the chart. Even if you don't add points later you may need to call createDefaultAxes() anyway, I don't know.

And no comes a reply to myself ! We figured out how to hack towards the behaviour we need. 1/ we add an ObjectiveC .mm file to the project, to call somme MacOS Cocoa's stuff 2/ At application AppB startup, from this ObjectiveC file we call [NSApp hide:nil] which "hides" the application, and reactivate our AppA. Well... This turns into some flickering of the active application (because AppA looses for a few ms activation when AppB starts ; then AppB hides itself and AppA gets the active app again), but we can live with that ! Thanks

@jsulm said in Class to add a footer to the QTabWidget widgets: @odelaune Simply put your QTabWidget and and the TabFooter in same vertical layout... Oh, yes of course. Thank you.

@JonB Thank you for your kind reply..I finally sort out the problem..but there's a 1 to 1.5 seconds delay in output..

@GKLC By now I suggest you produce a 20-odd line standalone minimal example. Reduce to absolute least which produces behaviour. May not apply to you, but 50% of the time we ask for this the OP discovers the issue. Try for yourself just starting anew from a QTreeWidget.

@JackMyson said in Developing QScintilla based application then crashes: BrStormTextMainWindow::handleTabChanged(int) I guess this is something you implemented? What are you doing there? According to the stack trace a tab is removed (QTabBar::removeTab(int)) and then BrStormTextMainWindow::handleTabChanged(int) is called - I guess you are trying to access something already deleted.

@Mihan Try Multimedia with the second "m" in lowercase

@tgbe Unfortunately there's a bit of time between creating a widget, showing it and it starting to process events, so the click that caused it to be created can't be directly forwarded to it. The way I usually deal with it is synthetize a dummy press and release events and send them to the widget using postEvent() once it's shown. Since there are multiple possible trigger types you can override editorEvent() to check what type of event caused the edit (click, keyboard etc.) and get the mouse position for the dummy click. I do this often enough that I wish this was a built-in option in the Qt delegates, but sadly it's not, so here we are.

Hi all, I've the same problem... anyone found a way to disable renegotiation?

@OPit said in QDataStream default LittleEndian: why LittleEndian is always used with writeRawData Because writeRawData writes a bunch of bytes and byte order is not relevant for it. Byte order is only relevant for things like integers, floats, ... (for data types bigger than one byte).