currently trying to add a themed entry area in shape of a tiny island.
Four months after this comment, where community interest was recognized, I find this incredibly sad once more.
It should not need a ton of upvotes to recognize a useful feature. Having the ability to scale stuff would be useful. This is self evident by KiCad's own library - if you include several sizes of OSHW Logos, you already noticed something is missing. You just jumped to the wrong conclusion.
Gitlab could immensely benefit from ActivityPub IMO. It is one of the go-to code forges for open source developers but also for companies that want more control over their hosting environment. ActivityPub could have bridged those worlds. It could have been a puzzle piece in "how do we figure out federated pull requests" and stuff like that.
The main reason Github is so big, is, because Github is so big. Everyone has an account there. Contributing is relatively frictionless. On Gitlab? Well, still big, still well-established. On self-hosted Gitlab? Hell no. I'm not creating hundreds of accounts for that.
It's sad you don't see that as a priority, because to me it is the USP of Gitlab. And ActivityPub could have made it much stronger.
I somehow suspect "efforts elsewhere" will just get us yet another "hey, here's how we cram AI in another nook" things. Please don't let it be that, OK?
currently trying to add a themed entry area in shape of a tiny island.
I have no idea how this came about. I just tried getting into debugging this again, and my keyboard was recognized instantly. I am assuming that ckb-next (which I tried last time) may have updated the keyboard's firmware or something like that.
It is now running all the way back to 0.71 and of course also in the current release 0.8 / fb88964b
The relevant log lines have changed to:
[Info:] ------------------------------------------------------
[Info:] | Detecting HID devices |
[Info:] ------------------------------------------------------
[Debug:] [1B1C:1B36 U=0004 P=0xFFC2 I=1] Corsair - Corsair Gaming K70 LUX Keyboard
[Trace:] [ResourceManager] Calling detection progress callbacks.
[Debug:] [Corsair K70 LUX] is enabled
[Trace:] [ResourceManager] Calling detection progress callbacks.
[Debug:] [Corsair peripheral] Device opened. VID/PID 1B1C:1B36
[Debug:] [Corsair peripheral] Device type C0
[Info:] [Corsair K70 LUX] Registering RGB controller
[Trace:] [ResourceManager] Calling device list change callbacks.
[Verbose:] [Corsair K70 LUX] successfully added
[Debug:] [1B1C:1B36 U=0001 P=0x000C I=0] Corsair - Corsair Gaming K70 LUX Keyboard
[Trace:] [ResourceManager] Calling detection progress callbacks.
[Debug:] [1B1C:1B36 U=0002 P=0xFFC0 I=0] Corsair - Corsair Gaming K70 LUX Keyboard
[Trace:] [ResourceManager] Calling detection progress callbacks.
[Debug:] [1B1C:1B36 U=0003 P=0xFFC2 I=0] Corsair - Corsair Gaming K70 LUX Keyboard
[Trace:] [ResourceManager] Calling detection progress callbacks.
[Debug:] [1B1C:1B36 U=0006 P=0x0001 I=0] Corsair - Corsair Gaming K70 LUX Keyboard
[Trace:] [ResourceManager] Calling detection progress callbacks.#1124 and !1467 added support for the Corsair K70 LUX keyboards (not RGB!). With the most-recent master build (4d4c18f1 at the time of writing) my keyboard does not show up, though. The log says [Corsair peripheral] Device type 00, Device type is unknown and finally [Corsair K70 LUX] is not initialized.
Here are the relevant parts from the log:
[Info:] ------------------------------------------------------
[Info:] | Detecting HID devices |
[Info:] ------------------------------------------------------
[Debug:] [1B1C:1B36 U=0002 P=0xFFC0 I=1] Corsair - Corsair Gaming K70 LUX Keyboard
[Trace:] [ResourceManager] Calling detection progress callbacks.
[Debug:] [1B1C:1B36 U=0003 P=0xFFC2 I=1] Corsair - Corsair Gaming K70 LUX Keyboard
[Trace:] [ResourceManager] Calling detection progress callbacks.
[Debug:] [Corsair K70 LUX] is enabled
[Trace:] [ResourceManager] Calling detection progress callbacks.
[Debug:] [Corsair peripheral] Device opened. VID/PID 1B1C:1B36
[Debug:] [Corsair peripheral] Device type 00
[Debug:] [Corsair peripheral] Device type is unknown
[Info:] [Corsair K70 LUX] is not initialized
[Debug:] [1B1C:1B36 U=0006 P=0x0001 I=1] Corsair - Corsair Gaming K70 LUX Keyboard
[Trace:] [ResourceManager] Calling detection progress callbacks.
[Debug:] [1B1C:1B36 U=0006 P=0x0001 I=0] Corsair - Corsair Gaming K70 LUX Keyboard
[Trace:] [ResourceManager] Calling detection progress callbacks.
[Debug:] [1B1C:1B36 U=0001 P=0x000C I=1] Corsair - Corsair Gaming K70 LUX Keyboard
[Trace:] [ResourceManager] Calling detection progress callbacks.
[Debug:] [1B1C:1B36 U=0004 P=0xFFC2 I=2] Corsair - Corsair Gaming K70 LUX Keyboard
[Trace:] [ResourceManager] Calling detection progress callbacks.OS - Windows Windows 11 / 22H2. Yes, I did run the program once with administrative privileges.
Nothing out of the ordinary, I pretty much only have this keyboard.
I have confirmed that the keyboard works under Linux with ckb-next.
I tried changing this line to 0x00 just to see what happens. The keyboard then shows up in the devices list, but I can't change any LED lights.
This is still the case in release 0.8
#1124 and !1467 added support for the Corsair K70 LUX keyboards (not RGB!). With the most-recent master build (4d4c18f1 at the time of writing) my keyboard does not show up, though. The log says [Corsair peripheral] Device type 00, Device type is unknown and finally [Corsair K70 LUX] is not initialized.
Here are the relevant parts from the log:
[Info:] ------------------------------------------------------
[Info:] | Detecting HID devices |
[Info:] ------------------------------------------------------
[Debug:] [1B1C:1B36 U=0002 P=0xFFC0 I=1] Corsair - Corsair Gaming K70 LUX Keyboard
[Trace:] [ResourceManager] Calling detection progress callbacks.
[Debug:] [1B1C:1B36 U=0003 P=0xFFC2 I=1] Corsair - Corsair Gaming K70 LUX Keyboard
[Trace:] [ResourceManager] Calling detection progress callbacks.
[Debug:] [Corsair K70 LUX] is enabled
[Trace:] [ResourceManager] Calling detection progress callbacks.
[Debug:] [Corsair peripheral] Device opened. VID/PID 1B1C:1B36
[Debug:] [Corsair peripheral] Device type 00
[Debug:] [Corsair peripheral] Device type is unknown
[Info:] [Corsair K70 LUX] is not initialized
[Debug:] [1B1C:1B36 U=0006 P=0x0001 I=1] Corsair - Corsair Gaming K70 LUX Keyboard
[Trace:] [ResourceManager] Calling detection progress callbacks.
[Debug:] [1B1C:1B36 U=0006 P=0x0001 I=0] Corsair - Corsair Gaming K70 LUX Keyboard
[Trace:] [ResourceManager] Calling detection progress callbacks.
[Debug:] [1B1C:1B36 U=0001 P=0x000C I=1] Corsair - Corsair Gaming K70 LUX Keyboard
[Trace:] [ResourceManager] Calling detection progress callbacks.
[Debug:] [1B1C:1B36 U=0004 P=0xFFC2 I=2] Corsair - Corsair Gaming K70 LUX Keyboard
[Trace:] [ResourceManager] Calling detection progress callbacks.OS - Windows Windows 11 / 22H2. Yes, I did run the program once with administrative privileges.
Nothing out of the ordinary, I pretty much only have this keyboard.
I also tried with this artifact: https://gitlab.com/CalcProgrammer1/OpenRGB/-/jobs/3220614068 but it gives me the same Device Type 00 is unknown /// Device is not initialized - how would this be initialized?
this is the log output:
....
[Info:] ------------------------------------------------------
[Info:] | Detecting HID devices |
[Info:] ------------------------------------------------------
[Debug:] [0451:82FF U=0001 P=0xFFB0 I=-1] -
[Trace:] [ResourceManager] Calling detection progress callbacks.
[Debug:] [1B1C:1B36 U=0002 P=0xFFC0 I=1] Corsair - Corsair Gaming K70 LUX Keyboard
[Trace:] [ResourceManager] Calling detection progress callbacks.
[Debug:] [1B1C:1B36 U=0003 P=0xFFC2 I=1] Corsair - Corsair Gaming K70 LUX Keyboard
[Trace:] [ResourceManager] Calling detection progress callbacks.
[Debug:] [Corsair K70 LUX] is enabled
[Trace:] [ResourceManager] Calling detection progress callbacks.
[Debug:] [Corsair peripheral] Device opened. VID/PID 1B1C:1B36
[Debug:] [Corsair peripheral] Device type 00
[Debug:] [Corsair peripheral] Device type is unknown
[Info:] [Corsair K70 LUX] is not initialized
[Debug:] [1B1C:1B36 U=0006 P=0x0001 I=1] Corsair - Corsair Gaming K70 LUX Keyboard
[Trace:] [ResourceManager] Calling detection progress callbacks.
...
[Debug:] [1B1C:1B36 U=0006 P=0x0001 I=0] Corsair - Corsair Gaming K70 LUX Keyboard
[Trace:] [ResourceManager] Calling detection progress callbacks.
...
[Debug:] [1B1C:1B36 U=0001 P=0x000C I=1] Corsair - Corsair Gaming K70 LUX Keyboard
[Trace:] [ResourceManager] Calling detection progress callbacks.
...
[Debug:] [1B1C:1B36 U=0004 P=0xFFC2 I=2] Corsair - Corsair Gaming K70 LUX Keyboard
[Trace:] [ResourceManager] Calling detection progress callbacks.
...(yes I did start once with administrative privileges)
It shows up in the list of supported devices, and the "scan for devices" bar at the bottom shows the name for a split second, but I don't get it into the devices list (only entry here is my mainboard).
Tested with artifact from https://gitlab.com/CalcProgrammer1/OpenRGB/-/pipelines/676861798 on windows 11.
from the logs, I think this is built using qt 5.15.3-1, and I've seen similar bug reports here: https://forum.qt.io/topic/124947/error-running-windeployqt/9 - there it is suggested that later versions (5.15.4+ or 6.10+) might have this one fixed.
I have pretty much zero experience with qt, so please take it with a huge grain of salt.
(edit: i removed the second link, I am not certain that it was not applicable to this problem)
This is marked as closed, but the most-recent nightly for windows is from four months ago (commit 30c8df58). Would it be possible to request a newer nightly so I can test if this fixes the problem for me?
I have a very similar problem with text objects, but I am not at any screen scale (I'm using the default 100% on windows). I would like to try if this is now fixed or if I should raise a different issue.
It is an issue common enough that I think it should have a formal way of addressing it.
Updating the description would mean that every app might handle this slightly differently. Ultimately this is something I would like to be able to filter while searching. I usually don't want to start using new apps that are abandoned already (continuing to use abandoned apps is fine; taking them up is not).
NoSourceSince seems to have different semantics attached to it. But I might be wrong.
I did not know an Archive repo existed, but it does not apply to the four examples given above - all of them seem to be in working condition.