openmacroboard / openmacroboard.sdk Goto Github PK

Not working in .net framework 3.5

Currently the "attachable" feature .WithButtonPressEffect() just scales down the image. This results in quite sharp edges which look a bit out of place because the stream deck buttons themselves have rounded corners.

So a new config should be added to allow for rounded corners on the shrunk images.

This feature is related to #11

Reproduce:

• Press virtual button down with LMB
• Mouse mouse outside the button hit-scan area
• Release LMB
• Note that the virtual button is still pressed

Expected

• Press virtual button down with LMB
• Mouse mouse outside the button hit-scan area
• As soon as the cursor leaves the button area, the virtual button should be released.

I cannot use this lib on my .netcore, any plans to support this?

netcoreapp3.1

I am using the version of 3.0.0, but after i update to last version 5.0.0, can't build the project now.
I see there have no "KeyBitmap.Create.FromGraphics" on the version 5.0.0.
So there have another method to instead of it?

First of all, my compliments about your library. It is really easy to use and well documented, keep up the good work!

If you have some time left it would be great is you can add a Property that enables "Make image smaller on button down". What do i mean? Well lets say the image is 100,100 when i push the button i would like to see that the image would be downsized to let's say 80,80 and when i release the button it returns to it's original size 100,100

This way the push action of a button is more like a software button. I noticed this behaviour if you use the stock StreamDeck software.

At the moment i have to discover every diferent Macroboard by my selve

Whats missing is a static Methode which returns all Availlable IMacroBoards

I am tinkering with setting GPU rendered graphics on a key. The GPU textures are always float4 (always with alpha channel, regardless of the fact if it is used or not). Now when reading these textures back from GPU to byte arrays it is at minimal cost (just a copy of the vram) but i am stuck with 4 channels. now stripping the 4th channel from that array requires a costly loop over the whole array. i would like to avoid that step.
I wish there would be at least BGRA32 or a more common RGBA32 option beside the BGR24 format. I understand that there is no point to care about the alpha channel on a key and omitting alpha reduces the amount of data to be sent. I wonder if one could still provide 4 channel images and the lib could just skip the 4th channel when sending the data to the device? sorry if i get anything wrong about how that works, i just wonder if the lib could be more convenient in case the source data is not BGR24.

I just started using this dependency in my app, and I noticed it's dependencies cannot be updated to the latest version: https://www.nuget.org/packages/OpenMacroBoard.SDK/2.1.0

System.Drawing.Common has released version 5.0.0, and this dependency blocks it from being updated. Are there breaking changes in 5.0.0 that impact OpenMacroBoard?

Any chance you will update this to have support for deckboard's virtual deck? https://deckboard.app/ It seems to be a reasonable freeware clone to StreamDeck. Teaching classes this fall and this would be nice to have for added powerpoint support and other things.

and communicate with the host via local TCP/IP or named pipes. Maybe grpc?

Hi, there! You have some great libraries for the Elgato StreamDeck on Windows.

I am wondering about Mac Support, or if you could point me in the right direction to get something going myself in C# to be able to interact with the StreamDeck (not by making a plugin). I'm trying to make a game for a game jam with the StreamDeck, and hoping to be able to bring something in to use in Unity with C#. Im on OS X.

StreamDeckSharp using 4.6.1
OpenMacroBoard.SDK 4.5.1

Please update OpenMacroBoard.SDK to 4.6.1

In the KeyPositionCollection constructor accepting dx and dy, I'd expect to see assignments:

KeyDistanceX = dx;
KeyDistanceY = dy;

... but they're not there, so the gap is always reported as 0 pixels.