Hi,
Just saw this in 5.5.0-2023-11-24 r32358 / 9b8c823 (and self-built Slicer):
A double click on slice views or 3D views has no effect. Usually, the view is maximized or minimized. There’s a button and a menu item to do this, just reporting.
Regards.
Hmm, that’s not a good regression. I have gotten used to that feature. I can confirm the same issue on today’s preview on my linux system.
I wonder if it’s related to this: Improve Event Delegation in qMRMLThreeDView and qMRMLSliceView by jcfr · Pull Request #7311 · Slicer/Slicer · GitHub
@chir.set I can confirm this on my local build and with a download of the current preview.
Can you file an issue on github?
Unfortunately, I can no longer log in my github account since they required 2FA as mandatory, which is a no-go to me for such a service. Github is no longer a welcoming place because they changed initial rules.
I understand that things always change with time, that’s life. Github is free to define its policies, the user is free to define his policies as well. And there’s more I can’t do because of this.
Regretfully, I won’t be able to file this issue.
Ah, yes, sorry, I recall now.
I’ll file and issue so we can get this resolved.
This is not a github thing. 2FA had to become part of our basic cyber hygiene due to bad actors becoming increasingly sophisticated. It is no longer optional or for high-value targets only, but unfortunately it is a must for everyone.
The good news is that setting up 2FA in github is very simple and it does not affect daily work at all, because you only need to authenticate a device once. I was postponing adding 2FA to my github account for a while, too, because I was afraid that it would complicate my access, but it turned out to be a non-issue. Github offers many 2FA options, so you should be able to find one that you like. First time you set it up and decide about which options you prefer may take 10-20 minutes, but setup of subsequent devices should take just 10-20 seconds extra (and you only need to authenticate each device only once).
I’ll give it a second look, only because I made previous contributions to extensions.
The problem will be in the future. Initially, there was a single password, like with many other services (mail, bank, tax department…). Then github (and others) mandated application passwords, their ‘personal access token’. Now it’s 2FA.
Next it will be browsers (discourse and others already do that), then such ISP would be required, such device brand, facial recognition, fingerprint of the fourth right toe, country of birth … These guys are caught in a whirlwind of paranoia, no one knows how all this will end up, my bet is nothing effective.
A second look, as time permits, only because I made previous contributions to extensions.