Im totally unsure. I did average in calc I, I got a 95 all up until the final which dropped me to an 87.
THIS IS NOT COMPLETE!!
I will likely continue to work on this. I was planning on releasing my full documentation soon, but with engineering courses I'm going to be working on it a LITTLE less. I'll be adding more after Friday.
For now - I've gotten the basic outline stated on how you can set it yourself. Full CEC compatibility using the PulseEight adapter - which I know has been giving everyone at least a little trouble.
I still have to edit and add my example .service and .sh files -
and to note - my example tv-off.sh script DOES NOT use the actual CEC Command, it sends the "on 0" command in LibCEC or wherever it came from. It works for some and it doesn't for others. As explained, if it doesn't work for you, get the CEC command being sent with TV off and echo that instead.
FOR NOW. This is proving the concept and is at least the basic documentation to do it yourself. Any questions, don't be afraid to ask -
If anyone wants to help with a fresh system, I'd love the assistance so I can get the docs perfected to be clear and concise for someone doing a fresh install.
If this gets enough traction I will potentially package this into a UI, as opposed to having to manually create the scripts yourself - though that is going to require a lot more work. We'll see.
When I have a touchscreen portable monitor connected, and keyboard disconnected - I tap a textbox on the surface: keyboard pops up on surface. good!
If i tap textbox on the other touchscreen, the keyboard pops up on that monitor. That's bad.
No matter how hard I try to relocate, shift, or move the keyboard, it always NEEDS to be on the secondary monitor if I tap a text field on that monitor
Is there is no way to lock the windows touchscreen keyboard to the primary monitor? why would they expect people to switch between displays to type?