Future Qwt updates

[Paul J]

FYI,

Whilst searching for Qwt information, I found this summary and repo on Github.

It suggests that the Qwt author has ceased maintenance, so possibly this might be a future option for GC ?

https://github.com/czyt1988/QWT?tab=readme-ov-file#overview

[Ale Martinez]

Hi Paul, I have not seen an official statement about Qwt end of maintenance, and Uwe seems to be responding support requests on newer Qt versions like this one for Qt 6.10: https://sourceforge.net/p/qwt/mailman/qwt-interest/thread/001401dc5ad9%24657b3a50%243071aef0%24%40perdrix.co.uk/#msg59262322, anyway it is something to be alert.

On a related note, Qt Charts used for all most recent charts replacing Qwt is marked for deprecation on Qt 6.10, it is still included but at some point in the future (may be 6.12 lts?) they could drop it, the proposed replacement (Qt Graphs) is fairly new and migration doesn't seem trivial either. They promise better performance enabling multiplatform hardware acceleration, which was an issue on Qt Charts, but I don't know anymore.

This is an interesting discussion to have, cheers, Ale.

[Ale Martinez]

PS: I see you started to create PRs to remove deprecation warnings on Qwt, please don't.

To remove deprecation warnings may be useful to ensure it continues to work con future Qt versions, if you want to do that and test with Qt 6.9.3, 6.10.1 or 6.11 beta, please do on your fork or otherwise, but as we previously discussed AppVeyor is currently a bottleneck and there is no need to use the shared instance for this, thank you. 

[Paul J]

I appreciate the GC AppVeyor bottleneck , so I now always build on my AppVeyor account before creating PRs.

I just forgot about the Qwt caching in AppVeyor, so I've updated my clean_build script to skip tidying the Qwt folder. 

[Ale Martinez]

El lunes, 5 de enero de 2026 a la(s) 6:29:13 p.m. UTC-3, Paul J escribió:

I appreciate the GC AppVeyor bottleneck , so I now always build on my AppVeyor account before creating PRs.

I just forgot about the Qwt caching in AppVeyor, so I've updated my clean_build script to skip tidying the Qwt folder. 

Hi Paul, in this case I thought we already agreed to leave Qwt along until a new version is necessary in https://github.com/GoldenCheetah/GoldenCheetah/issues/4750, currently it can be build with Qt 6.9 and 6.10 without issues AFAIK and there are not new developments on GC using it, so we are Ok for a while.

On more general terms I appreciate your willingness to collaborate features and fixes, but your insistence on non-functional refactoring is becoming increasingly annoying for me.

We have several planning related features you could work on if you like to: https://github.com/GoldenCheetah/GoldenCheetah/issues?q=is%3Aissue%20state%3Aopen%20label%3APlanning, in particular managing Text Cues in Workout Editor or Import/Export of FIT workouts are self-contained and nice to have for v3.8.

Cheers and thanks for your contributions, Ale.

[Paul J]

Hi Ale,

    I'm happy to look at the Import/Export of FIT workouts so they are self-contained.

   Would you mind looking at/testing https://github.com/GoldenCheetah/GoldenCheetah/pull/4730 ? As it ensures filtered charts display the correct information in certain cases.

   And finally, regarding the issue of non-functional refactoring (https://github.com/GoldenCheetah/GoldenCheetah/pull/4795) this will be the last refactoring PR you will get from me.   The reason why I have proposed it is that creating additional views requires many code changes, and 4795 hopefully reduces them, as I have been thinking about the additional view for https://github.com/GoldenCheetah/GoldenCheetah/issues/3327, whilst also maintaining my own branches equipment management view PR(https://github.com/paulj49457/GoldenCheetah/tree/shared-xml-equipment-management-feature). 

Regards,

Paul.

[Ale Martinez]

El martes, 20 de enero de 2026 a la(s) 2:56:11 p.m. UTC-3, Paul J escribió:

Hi Ale,

    I'm happy to look at the Import/Export of FIT workouts so they are self-contained.

Great, I will assign to you.

 

   Would you mind looking at/testing https://github.com/GoldenCheetah/GoldenCheetah/pull/4730 ? As it ensures filtered charts display the correct information in certain cases.

I commented on this, IMO it is a non-starter since it breaks click-thru behavior.

 

   And finally, regarding the issue of non-functional refactoring (https://github.com/GoldenCheetah/GoldenCheetah/pull/4795) this will be the last refactoring PR you will get from me.   The reason why I have proposed it is that creating additional views requires many code changes, and 4795 hopefully reduces them, as I have been thinking about the additional view for https://github.com/GoldenCheetah/GoldenCheetah/issues/3327, whilst also maintaining my own branches equipment management view PR(https://github.com/paulj49457/GoldenCheetah/tree/shared-xml-equipment-management-feature). 

I will take another look in a few days, but in the future I suggest you to use the forum to discuss changes before you invest your time coding them.

Cheers, Ale.