Colore - C# Library for Chroma

Discussion in 'Razer Chroma' started by BrandonJCScott, Mar 8, 2015.

Thread Status:
Not open for further replies.
  1. Sharparam

    Sharparam Member

    There doesn't seem to be much information about the error in their documentation. Did you make sure to close Synapse before running the code?
     
  2. veGz_

    veGz_ New Member

    Hello guys! Is there anyway to run this lib with SKD v0.4.8? I think i tried everthing already :D I'm getting this error:
    Code:
    An exception of type 'System.TypeInitializationException' occurred in Corale.Colore.dll but was not handled in user code
    
    Additional information: The type initializer for 'Corale.Colore.Razer.NativeMethods' threw an exception.
    on
    Code:
    var keyboard = Corale.Colore.Core.Keyboard.Instance;
    I used all 4 branches from gitHub.
    Did I miss something important?
    Cheers
     
  3. Sharparam

    Sharparam Member

    Updates to support 0.4.x of the SDK are underway. Ran into a minor (or perhaps it's bigger than that) issue that is delaying a release.

    Tracking issue.

    Edit: As is too often the case, the fix was figured out shortly after creating the issue. I'll try to push out an update shortly, assuming our change in CI worked without errors!
     
    Last edited: Sep 5, 2015
  4. Sharparam

    Sharparam Member

    njbmartin likes this.
  5. BrandonJCScott

    BrandonJCScott Active Member

    Colore 2.1.0 has just shipped! This supports .NET Framework v3.5 allowing for Unity related development.

    Get it from GitHub or NuGet!
     
    njbmartin likes this.
  6. Looks interesting
     
  7. njbmartin

    njbmartin Developer of Awesome

    The biggest thing to happen to Colore since Colore.
     
  8. xkisu

    xkisu Member

    For those of you getting the "System.TypeInitializationException" memory errors, you need to set your Framework to 3.5 in your project properties.

    Just spent an hour working through the error, and then realized I didn't check what framework colore was built against. :stuck_out_tongue_winking_eye:
     
  9. njbmartin

    njbmartin Developer of Awesome

    It supports .NET Framework 3.5+, so unless you were using something lower than that, it should have been fine.
     
  10. xkisu

    xkisu Member

    I was trying to use 4.5, and it kept giving me the memory access errors some other people who posted on where where getting.

    It didn't start working until I changed my project framework to 3.5
     
  11. njbmartin

    njbmartin Developer of Awesome

    Hmm, one of my own projects is targeting 4.5, so I'm not sure it's specifically an issue with the Colore library. Are you targeting Any CPU, 32-bit or 64-bit?
     
  12. xkisu

    xkisu Member

    Any CPU, and Colore is the only other library I have referenced besides the standard system libraries
     
  13. Cyfl0w

    Cyfl0w New Member

    I keep getting the same error :/
     
  14. Sharparam

    Sharparam Member

    @KeithM @Cyfl0w Are you using the latest (at the time of writing: v2.2.1) version of Colore from either the GitHub release page or NuGet package?

    Under what framework targets are you compiling and what (full) error messages are produced?

    Did the issues appear in projects already using Colore and then updated to the 3.5 version? Is the issue exhibited in a new project targeting 4.5 and then referencing v2.2.1 of Colore?
     
  15. xkisu

    xkisu Member

    I'm using the latest version of Colore from the NuGet package, this is a new project so I'm not updating from any previous Colore version.

    I was trying to compile under .NET 4.5, and this is the error message it would throw:

    ..Wait a sec, this is weird.

    So I switched it back to 4.5 so I could get the error to paste here, but now it's not throwing it, and everything is working fine in 4.5 and 3.5. I don't know what happened there.

    @Cyfk0w Try changing your Target Framework to 3.5 and see if it fixes it. It did for me for some reason. You'll probably have to re-install the Colore and log4net package(s) after the switch if your using the NuGet package.
     
  16. Sharparam

    Sharparam Member

    @KeithM Interesting, I'll create a new WPF project targeting 4.5 and see if I get similar results. Will edit this post when done.

    EDIT: Bug in Colore found and fix being deployed as we speak.
     
    Last edited: Oct 3, 2015
  17. Cyfl0w

    Cyfl0w New Member

    I fixed it with setting my project target from 4.5.2 back to 4.5 :)
     
  18. xkisu

    xkisu Member

    Great!
     
  19. xkisu

    xkisu Member

    Is there a way to pass SetKey a keycode instead of a key instance?

    Like instead of:
    Code:
    Keyboard.Instance.SetKey(Key.LeftControl, Color.Blue);
    You could do:
    Code:
    Keyboard.Instance.SetKey(17, Color.Blue);
    Currently the only way I can see me doing it is to create a Dictionary with the keycodes and their Colore Key counterparts, but I wanted to see if there was a easier way first ;)
     
    Last edited: Oct 3, 2015
  20. Sharparam

    Sharparam Member

    KeithM likes this.
Thread Status:
Not open for further replies.
Sign In with Razer ID >


Don't have a Razer ID yet?
Get Razer ID >