Stefan Sauer
Stefan Sauer
For some of the UI issues I am afraid the pace of the OSS community is to blame. I've started buzztrax on gtk+2, posted to gtk-3 and replaced deprecated gnome-canvas...
Also going from QT4 to 5 (or from 5 to 6) is not without pain. And rewriting everything from c to c++ is not easy peasy either. In the end...
We can add a --args key=value options that can be specified multiple times. If no graph is given on the commandline we ignore them. Otherwise: - we create a on-the-fly...
+1 for `button.ev3_keys`, or maybe just `button.keys` `button.key_pressed(k)` is good. maybe instead of `button.keys_pressed` -> `button.any_key_pressed()` (which would just check for `keys_pressed()` not returning an empty list)
I don't think I'd miss them. For those I would probably rather write: ``` if buttons.left.isPressed(): go_left() ``` Given that there are just 6 keys, changes that two will be...
Thanks!
Just confirming, I was indeed looking for something that returns true if any key is pressed. That is useful when e.g. showing an error.
Hubble UI doesn't work, fresh Cilium 1.12.1 install, "Data stream has failed on the UI backend: EOF"
Get same error asin in first comment and the same logs as Pascal. Using cilium v1.11.8 and just downloaded latest hubble and cilium binaries today. Here is the relay: ```...
gtk-doc tries to instantiate code to introspect them. Since I have not touch neither project, I'Ve tried to rebuild, but get trapped by -Werror and deprecated gtk+ api that has...
``` ./autogen.sh --enable-deprecated --disable-debug --enable-gtk-doc ``` and it build here. I'll take a closer look on the weekend to see if I can do some more cleanups.