QCAD.org Forum

Don't know whether it is a problem of my desktop (KDE Linux) or my mouse or QCAD...
(plus, I have vague feeling it has been discussed before?)
but just in case I am missing something obvious:
when I select layer to activate in Layer List window, the selection does not remain persistent
just moving mouse cursor anywhere in Layer List window, without clicking anything changes active layer

most peculiar
any ideas anyone, please

QCAD Professional
Version: 3.32.3.1 (3.32.3.1)
Internet: QCAD.org
Build Date:Jun 5 2025
Revision: e471b5e
Qt Version: 6.6.0
Architecture: x86_64
Compiler: gcc 11.4.0

an update:
3.32.2 (details below) works fine
where do I report the issue, please?
(both 3.32.3 and 3.32.3.1 are affected by the problem)

QCAD Professional
Version: 3.32.2.0 (3.32.2)
Internet: QCAD.org
Build Date: Feb 20 2025
Revision: 6616def
Qt Version: 5.14.2
Architecture: x86_64
Compiler: gcc 5.4.0

Hi,

The best place to report a bug is on QCAD Bugtracker.

Regards,
CVH

CVH wrote: ↑

Sun Aug 17, 2025 7:40 pm

...best place to report a bug is on QCAD Bugtracker.

thank you, done
https://qcad.org/bugtracker/index.php?d ... sk_id=2689

Clarification by reporter: only the current development snapshot 3.32.3.1 seems to be affected. Only particular Linux distributions / window managers appear to be affected (MX Linux, KDE).

andrew wrote: ↑

Mon Aug 18, 2025 4:23 pm

... Only particular Linux distributions / window managers appear to be affected (MX Linux, KDE).

Thank you for all the additional testing.

re-installing MXlinux solves the problem
I guess my original installation (same on three PCs) must have got corrupted?

an update:
not just re-installing MX works but also (and rather simpler) cleaning up old QCAD config file before moving from Qt5 to Qt6 works.
I no longer have any strange problems with my rodent having his own opinions about what to do ...

Hi,

It is known that resetting the QCAD configuration may solve weird problems.
Not that there is a preference stored in there that could explain your problem or those of other users before.

After deleting and re-installing a new QCAD version it would be my second option while troubleshooting.
I then usually rename the former config file so that I can compare it with the newly created at startup.

Launch parameters may also have an influence.
For example:
-always-load-scripts is handy when experimenting with a new script but it may corrupt normal behavior.
-enable-script-debugger is not a stable environment.
Note that the debugger is said to be excluded for Qt6.


Even then I would stick to stable releases ... Those with 3 groups of digits, not with a fourth group.
Presumably still based on Qt5 except for some packages.
The current state is beyond snapshot v3.32.3.4 (Based on a Jul 11 commit)
Snapshots are test cases.

There is nothing to gain fundamentally with Qt6.
Unless QCAD is fully ported to Qt6 it is rather the inverse.

Porting may simply be implemented as a patch with an additional if-then-else clause to process.
Getting a pointer with getPtr(p) (Current state) from a shared pointer object using data() (Qt5) or implicitly (Qt6) is such an example.
Fast but also called very frequently.
Diversifying between Qt6 or 5 can be found at any level.

Regards,
CVH

CVH wrote: ↑

Wed Aug 20, 2025 4:53 am

...It is known that resetting the QCAD configuration may solve weird problems...

I didn't know this
It took me two days of experimenting and asking for help, to discover this

CVH wrote: ↑

Wed Aug 20, 2025 4:53 am

...After deleting and re-installing a new QCAD version it would be my second option while troubleshooting.
I then usually rename the former config file so that I can compare it with the newly created at startup.

excellent advice

CVH wrote: ↑

Wed Aug 20, 2025 4:53 am

Even then I would stick to stable releases ...

I normally do as well
In this case I was intrigued to try Qt6 version

CVH wrote: ↑

Wed Aug 20, 2025 4:53 am

...There is nothing to gain fundamentally with Qt6.
Unless QCAD is fully ported to Qt6 it is rather the inverse.

interesting
my (subjective) experience was that Qt6 snapshot I tried was noticeably faster than stable version with my complex/heavy files
of course correlation doesn't prove causation

BTW - while on the subject of "heavy" files
is there a way of obtaining statistic (e.g. number of blocks used etc) in a QCAD file to judge how complex the file is?
apart from an easy and obvious size of the file...