Looking For Most Appropriate/Efficient Way Of Resizing A Frameless Window

[wysota]

I would probably implement a "charm" that could be applied on a widget consisting of an event filter that would intercept mouse-move events and modify the geometry of the widget. If I wanted to have cursor changes while moving along the borders of the window I would also enable mouse tracking for the widget as part of my charm. One can also check the code for controlling sub-windows of QMdiArea.

[Sean]

Thanks for your opinion! I care a lot about how much computational resource my algorithm consumes and that's why I posted this thread in the first place. If I keep tracking the mouse inside the window and calculating the corresponding geometry, will that be too much computation for such a simple task? Since the code we write through regular C++/QT statements are user-level code, and there are machine/OS dependent instructions/APIs which utilize hardware acceleration for such purposes. And QT use lots of them internally to improve its efficiency, just like video game developers regularly utilize video card facilities.

[wysota]

Hardware acceleration or anything like it will not help you determine whether you are at a window border or not. If you want to have such information inside your application, you need mouse tracking. The only alternative is to rely on the windowing system by not applying a custom skin and using the default decorations instead.

[genjix]

just like video game developers regularly utilize video card facilities.

This is not the case. Engine developers do that and game developers use the engine. In the same way that gui library programmers handle the gritty details and application programmers use the library. Game programming is a large part scripting and setting up events. There's not much 3D programming done apart from writing the odd shader or maybe using a fragment program to speed a physics calculation (in extreme cases).

I can't pretend to know your situation here, but if you're using Qt then likely you're not resource stricken- why are you rolling your own gui?

[Sean]

You are right. I'll track the mouse by myself to implement the resizing code.

This is not the case. Engine developers do that and game developers use the engine. In the same way that gui library programmers handle the gritty details and application programmers use the library. Game programming is a large part scripting and setting up events. There's not much 3D programming done apart from writing the odd shader or maybe using a fragment program to speed a physics calculation (in extreme cases).

I can't pretend to know your situation here, but if you're using Qt then likely you're not resource stricken- why are you rolling your own gui?

Thanks for your advice! I'm gonna rely on what QT provides.