Yoooi0
Yoooi0
@nicolaihenriksen The `TargetType` in this case is not necessary. But I've tested it and it applied my custom style on all controls except those that have their own `FocusVisual` style...
> I think the problem with that is that the library itself does not ship with an App.xaml AFAIK; the demo app of course does, but that is not what...
> I would be surprised that you got any of the ones defined in MDIX since the SystemParameters.FocusVisualStyleKey is not used anywhere in the library. But since they are "the...
> After browsing a bit around, I stumbled upon https://github.com/dotnet/wpf/issues/1164 in the dotnet/wpf repo which is exactly what I see in bullet 2 above. Judging from that, and the associated...
> I had my solution setup to run the net472 version of the output, not the .NET7. Changing that allows me to override it correctly. Doh, didnt even think to...
Some examples/explanation for the proposal. Current sample device ```json { "name": "Sample Device", "messages": { "ScalarCmd": [ { "ActuatorType": "Vibrate" }, { "ActuatorType": "Position" } ], "RotateCmd": [ { "ActuatorType":...
Yea, I also thought about removing `RotateCmd` and having it be replaced with `ScalarCmd` with (-1, 1) range but I think there would also have to be a new actuator...
> The above solution won't quite fix this, because I still can't define two different SensorRead's on the same feature. I think you would not define two sensor Read message...
> So no, don't wanna take the raw/calibrated and run with it everywhere. It was just a way to talk about getting different units from the same feature. Oh yea,...
> It's easy to ignore for everyone who doesn't want it and it's easy to leave out for most of the devices that won't need it. Yup that's my thinking...