Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 15 18:42
    M1XT3NZ commented #280
  • Jan 15 13:07
    Sharparam commented #280
  • Jan 15 13:06
    Sharparam assigned #280
  • Jan 15 13:06
    Sharparam labeled #280
  • Jan 15 02:44
    M1XT3NZ opened #280
  • Jan 09 11:44

    Sharparam on 6.0.0

    Fix dead link Fix dead link (#277) Fix dead … (compare)

  • Jan 09 11:44
    Sharparam closed #277
  • Jan 09 11:44
    Sharparam commented #277
  • Jan 09 11:43
    Sharparam milestoned #277
  • Jan 09 11:43
    Sharparam assigned #277
  • Jan 09 11:43
    Sharparam labeled #277
  • Jan 09 11:42
    Sharparam edited #277
  • Jan 09 11:42
    Sharparam commented #277
  • Jan 09 09:43
    PerhapsSomeone commented #277
  • Jan 09 09:41
    PerhapsSomeone commented #277
  • Jan 08 21:18

    Sharparam on 6.0.0

    Update Cake tool versions (compare)

  • Jan 08 21:15

    Sharparam on 6.0.0

    Update test project to .NET Cor… Update tests Add icon and 1 more (compare)

  • Jan 08 20:24

    Sharparam on 6.0.0

    Implement Serializable properly… (compare)

  • Jan 08 20:07

    Sharparam on 6.0.0

    Disable CA1303 (compare)

  • Jan 08 19:55

    Sharparam on v6.0.0-rc6

    (compare)

Adrian
@WolfspiritM
I agree...handling remapped keys would be a way harder problem
Adam Hellberg
@Sharparam
Razer needs to provide a definite (this is important) list of ALL available physical layouts of the keyboard as well as provide a function that accurately returns the physical layout of the keyboard. Otherwise there is no reliable way to even try to handle it.
problem is that since they seem hellbent on putting this workload on the developers, every developer needs to implement their own solution to this since they won't add it natively in the SDK.
Adrian
@WolfspiritM
Or make their SDK light up the correct key no matter what Keyboard Layout...
Adam Hellberg
@Sharparam
people using Colore can use the methods in there of course, but those not using C# and working with the SDK directly will produce hundreds of duplicate methods to do this
Adrian
@WolfspiritM
It's one big flaw I saw in their SDK as I was playing around, that they didn't think of other keyboard layouts. Let's just hope they'll work on it.
Adam Hellberg
@Sharparam
Then you also have to consider that some people may have multiple keyboards plugged in with differing layouts
it's likely a small enough amount to be irrelevant, but still an interesting thought
Adrian
@WolfspiritM
not sure if that'd be so hard for their SDK that is doing the USB part to switch out keys (Y and Z for example) depending on the layout of the device it's sending to. Then it doesn't matter how many keyboards are plugged in
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