Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Dec 07 16:00
    PerhapsSomeone review_requested #277
  • Dec 07 16:00
    PerhapsSomeone opened #277
  • Nov 08 15:23
    iprisj edited #276
  • Nov 08 12:48
    iprisj opened #276
  • Nov 08 08:29
    Sharparam closed #275
  • Nov 08 08:29
    Sharparam commented #275
  • Nov 08 00:20
    iprisj opened #275
  • Sep 27 12:48
    MasterR8 closed #273
  • Sep 05 16:31
    MasterR8 commented #273
  • Sep 05 16:23
    Sharparam commented #273
  • Sep 05 16:07
    MasterR8 commented #273
  • Sep 03 09:46
    Sharparam commented #273
  • Sep 03 09:44
    Sharparam edited #273
  • Sep 03 09:44
    Sharparam edited #273
  • Sep 03 09:43
    Sharparam milestoned #274
  • Sep 03 09:43
    Sharparam commented #274
  • Sep 03 09:42
    Sharparam labeled #274
  • Sep 03 09:06
    poveden edited #274
  • Sep 03 09:06
    poveden opened #274
  • Aug 15 16:13
    MasterR8 opened #273
Adam Hellberg
@Sharparam
it's the reason this should be put in the driver so it's as close to the hardware as possible, or firmware even. but they've already released the keyboards so it's a bit late for that
the SDK doesn't (and probably won't for the foreseeable future) provide granular access to specific devices, only to "all <device type here>" so the SDK can't be used to filter devices out
Dariusz Niemczyk
@Palid
@Sharparam tbh from what I'm reading the SDK is a piece of crap.
Adrian
@WolfspiritM
Not really talking about the API part of the SDK...more the backend (driver) part that does the work. The driver knows what layout it is and it could fix this. However...it's totally Razers part to do that
Dariusz Niemczyk
@Palid
Wait. We should have access to the keyboard's product number, or sth.
this way we can at least try doing an ugly fix.
Model number*
Adam Hellberg
@Sharparam
you can query a GUID and get the device type and whether it's connected, not any details about its layout
see: DeviceType struct and Query method on Chroma class
DeviceInfo*
Dariusz Niemczyk
@Palid
Well, we can try with the Model Number then.
Adam Hellberg
@Sharparam
it cannot be queried
we can only get type of device (keyboard, mouse et.c) and whether it's connected
Dariusz Niemczyk
@Palid
@Sharparam you sure that it can't be queried? I'm not talking about SDK now.
Let's just agree that SDK sucks and try different methods. :P
Adam Hellberg
@Sharparam
you could probably start making your own stuff to read USB data, but then you're reverse engineering and breaking rules and shit
Adrian
@WolfspiritM
You could query the USB somehow
Dariusz Niemczyk
@Palid
tbh if Razer would start doing something against 'illegal rev-eng' in this case they would lose a lot of fanbase.
Adrian
@WolfspiritM
Even having the model...I think using InputLanguage.CurrentInputLanguage as an ugly workaround would be easier instead somehow mapping model/guid to region to key
Dariusz Niemczyk
@Palid
but yeah, let's not go into this discussion. :D
@WolfspiritM There's a problem with ugly workarounds: they are ugly and always do a problem in edge cases.
and here the edge case isn't even so edge-like.
Adrian
@WolfspiritM
Querying the USB for a model number is nothing more then a ugly workaround, too...
Dariusz Niemczyk
@Palid
True, but a bit more bulletproof.
Adam Hellberg
@Sharparam
@/all Whoever had issues with exceptions from UnInit can you try using feature/uninit-improvement and see if that fixes the issue?
Adrian
@WolfspiritM
@Palid I don't really see where it would be much more bulletproof. It won't fix multiple keyboards with different layouts nor remapped keys. But you can sure try querying USB :-)
@Sharparam I will try it later. Thanks!
Adam Hellberg
@Sharparam
@WolfspiritM also if you find issues with it please comment about them here: CoraleStudios/Colore#108
Adrian
@WolfspiritM
@Sharparam alright
Dariusz Niemczyk
@Palid
@WolfspiritM will do if I have some time this weekend
got so many tickets that I'll have to work overtime on the weekend :(
ok so i have my code above
and it keeps giving me this throw exception
any ideas on a work around or what i did wrong?
Nico
@njbmartin
That means that the ChromaSDK hasn't been enabled
Ryan Hill
@Aurous
yep... i thought i had enabled it.. i guess in the updates or something on my computer i needed to reenable it...
Nico
@njbmartin
In synapse, go to any chroma device and you'll see a Chroma Apps menu item. make sure "Chroma Apps" is enabled
yeah, the latest update to synapse adding this functionality made it disabled by default
certainly caught me out
Ryan Hill
@Aurous
I just used the reg file to enable, and the codes magically working, of course
Adam Hellberg
@Sharparam
reg files aren't used anymore since the release of the SDK
and integration in synapse
Nico
@njbmartin
yeah, that wasn't made clear to the dev community when synapse updated ;)
Ryan Hill
@Aurous
Do you even need to close synapse now? Or can you just leave it open?
Adam Hellberg
@Sharparam
i think there can still be issues with advanced profiles, but maybe they fixed that too
Ryan Hill
@Aurous
Ah, that's good
Nico
@njbmartin
not yet, the current public SDK version still has an issue with profiles overlapping
Ryan Hill
@Aurous
How would I use RGB with corale.colore.core.color?