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)

Bart van Vliet
@Kapulara
As key handler with event
Brandon Scott
@brandonscott
Perfect!
Nice job.
Bart van Vliet
@Kapulara
But it's not triggering Macro keys xD
Brandon Scott
@brandonscott
Does it work for any key>?
Brandon Scott
@brandonscott
Awesome
Adam Hellberg
@Sharparam
WinForms handles keys that propagate through the system, macro keys on the blackwidow are not system keys and are handled specifically by Razer's drivers. you cannot intercept them through regular system calls (and AFAIK razer doesn't expose anything to capture them)
Brandon Scott
@brandonscott
That is correct.
I wish they did though.
So you'; have to work with the System keys I'm afraid.
Bart van Vliet
@Kapulara
Yeah, Cause now i can't kinda detect whether or not the key is pressed :/
Brandon Scott
@brandonscott
Ignore Macro keys for now
Bart van Vliet
@Kapulara
Alrighty
Ah i could use them for navigating / menu etc.
OH no
I can't detect
....
Nvm. Il leave them blank :)
So now i have a KeyCode, Can i use a KeyCode with Colore?
Or do i have to convert it to numeric ?
I'm guessing this is a yes.
Brandon Scott
@brandonscott
@Sharparam Did something similar to this
Adam Hellberg
@Sharparam
i just manually mapped system keys to razer keys, as there's no efficient way to make an automatic mapping due to the philosophy of the designs
razer's key enums are defined based on grid location while system keys are defined based on some standard in the libraries
Bart van Vliet
@Kapulara
Do you have a source?
Bart van Vliet
@Kapulara
@Sharparam thank you so mutch! :heart:
Adam Hellberg
@Sharparam
these are for WPF keys, mind
you'll have to adapt it to the enum WinForms uses
Brandon Scott
@brandonscott
That must have been tedious @Sharparam
Adam Hellberg
@Sharparam
determination is a hell of a drug
Adrian
@WolfspiritM
Heya. :-) Till now I've send updates to the Keyboard all at once including sending already set Keys with Chroma.Instance.Keyboard.SetKeys(keys, Color); today I noticed that sometimes a change is not successfully send to the keyboard somehow. It seems to be random to me when it works and when it doesn't. If I repeat the SetKeys a few times in my method it always works (but that's just ugly). For now I've included a ColorCache to only send the keys that changed and that seems to work. Is there a known issue or limit of updates within a second (even so I don't think I'm hitting that)? Or can this have something to do with Threading? A lock around the SetKeys didn't work either.
Brandon Scott
@brandonscott
It should work every time you set it without doubt
there's no rate limiting
@Sharparam any thoughts?
Adrian
@WolfspiritM
Hm that's weird then. I even logged the request to setkeys and I'm pretty sure setkeys is called with the right color and key. But the Keyboard doesn't set the Color. A few calls later it finally does.
Adam Hellberg
@Sharparam
in WaM with frequent updates it would not always register every change (~250ms between changes). havent' checked with latest updates but if brandon could get 24fps working which is an update every ~41.67 seconds then anything down to at least that delay should work fine
milliseconds*
41.67 milliseconds
Adrian
@WolfspiritM
Sometimes there are updates every half a second for me and it seems to work with just a few keys. Just all Keys at once seem to be causing issues.
Adam Hellberg
@Sharparam
how are you performing the update when changing all keys
Adrian
@WolfspiritM
Multiple Chroma.Instance.Keyboard.SetKeys(new List<Key> { Key.W, Key.A, Key.S, Key.D }, Color1); for each color
Adam Hellberg
@Sharparam
a cache of some sort might be more performant in reducing the number of created objects on the heap, but it shouldn't be related to the issue. it should just change the speed of updates if there are a lot of such new object creations
is this single- or multithreaded app?
Adrian
@WolfspiritM
It's Multithreaded...using Tasks
Adam Hellberg
@Sharparam
@brandonscott are your updates in your apps handled by their own threads separate from main thread?
Brandon Scott
@brandonscott
No