Package Details: fsleyes 1.12.6-1

Git Clone URL: https://aur.archlinux.org/fsleyes.git (read-only, click to copy)
Package Base: fsleyes
Description: FSLeyes is the FSL image viewer
Upstream URL: https://fsl.fmrib.ox.ac.uk/fsl/fslwiki/FSLeyes
Licenses: Apache
Submitter: tobac
Maintainer: tobac
Last Packager: tobac
Votes: 5
Popularity: 0.000000
First Submitted: 2017-10-11 11:10 (UTC)
Last Updated: 2024-10-12 17:21 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

keiichiiownsu12 commented on 2019-07-27 19:35 (UTC)

no worries. Let me know if any of those previous packages I mentioned successfully integrate fsleyes with KDE's global menu, if you run in to the same problem as I, or if you find a better implementation/alternative!

tobac commented on 2019-07-27 19:21 (UTC) (edited on 2019-07-27 19:23 (UTC) by tobac)

Thanks anyway for your comprehensive explanation :)

Just a clarification: FSLeyes uses wxWidgets as its GUI toolkit.

keiichiiownsu12 commented on 2019-07-27 17:55 (UTC)

@tobac Nevermind, none of the qt4 aur packages are building correctly. . .

keiichiiownsu12 commented on 2019-07-27 15:08 (UTC)

@tobac actually, it seems fsleyes global menu does work with only the packages I mentioned. For whatever reason, when I load an image into fsleyes (usually 4D raw diffusion data), the program will stop showing the global menu, and won't show it on subsequent start ups. Fsleyes does lag on startup when loading the image, but that is because the image is loaded over an sshfs connection usually.

For whatever reason, global menu works now, even on multiple start ups, when no data is loaded. Weird?

keiichiiownsu12 commented on 2019-07-27 14:59 (UTC) (edited on 2019-07-27 15:02 (UTC) by keiichiiownsu12)

@tobac no, fsleyes does not work out of the box with KDE's global menu. If fsleyes is a gtk application like I believe (or does it have a qt implementation?), then the setup to get it to work should be similar to other GTK apps (e.g. libreoffice, etc.).

There were a few packages I had installed for other applications. Of these I am not sure which one exactly made it possible, but all of them were suggested, either on KDE's website or on forums for other GTK apps. This is a good reference: https://forum.manjaro.org/t/gtk-global-menu-in-plasma-5-13/42112

Packages needed are: appmenu-gtk-module (main one, apparently) libdbusmenu-glib/gtk2/gtk3/qt4/qt5 (libdbusmenu-qt4 is an AUR package) lib32-dbusmenu-glib/gtk2/gtk3/qt (lib32-dbusmenu-qt is an AUR package) appmenu-qt4 (AUR package)

Not sure which specific package made it work (would be good to test each). I have all but the lib32-libdbusmenu-qt, libdbusmenu-qt4, and appmenu-qt4 installed. I'll add each one sequentially and let you know which does the trick.

I.e. which one solves the issue I noted below*

tobac commented on 2019-07-27 09:03 (UTC)

@keiichiiownsu12 For me, FSLeyes doesn't work at all with Plasma's global menu widget, which I'm also a user of. Did it work out of the box for you?

keiichiiownsu12 commented on 2019-07-25 01:27 (UTC)

Builds and works fine. Having an issue in KDE with the global menu widget. If opened once, fsleyes will show its menu buttons in the global menu widget properly. However if I open and close it a second time, the menu options do not show (unless I disable the widget). Curious if anyone might know a way to diagnose the issue?

tobac commented on 2018-04-16 19:16 (UTC)

It worked reliably for me, I guess $startdir somehow wasn't defined in your build environment. Anyway, working with ${srcdir} is certainly neater. I modified the PKGBUILD accordingly.

fishburn commented on 2018-04-16 18:56 (UTC) (edited on 2018-04-16 18:56 (UTC) by fishburn)

This didn't work for me until I added the full path to the install commands

install -Dm644 "${srcdir}/$pkgname.png" "$pkgdir"/usr/share/icons/hicolor/512x512/apps/$pkgname.png

install -Dm644 "${srcdir}/$pkgname.desktop" "$pkgdir"/usr/share/applications/$pkgname.desktop

tobac commented on 2018-03-27 19:53 (UTC)

Switching to legacy wxPython (i.e. < 4.0) might indeed solve your problem:

https://github.com/wxWidgets/Phoenix/issues/743

This GitHub issue also supports my suspicion that it is (a) an upstream problem and (b) they are aware already. So let's hope it is fixed soon :)

« First ‹ Previous 1 2 3 4 5 6 Next › Last »