I have a node application that runs on a raspberry pi 4b and interacts with the user through some buttons and/or sensors. I want to display full-screen images to the user according to which stage they've reached by pressing or activating said buttons and sensors.
Related
Lets say i have a Linux (Ubuntu), well NVIDIA packaged one that comes with Jetson boards, and i have HDMI output and DP.
The goal is to: Display Desktop part via HDMI, and display GUI that i made with OpenGL via DP, but without DP ever showing Desktop, if process with GUI exits, the display connected via DP does not show anything until process is restarted.
So far i have researched X server, but most of the materials just talk about X11 protocol, and how to create a window. If i just open a window in full-screen mode, it could work, but until GUI is launched i would see part of Ubuntu desktop there.
The GUI is basically a Monitor with CT Overlay that sends touch input via I2C.
I have a computer that uses any loudspeaker as microphon and loudspeaker at once, no matter it's a build in, connected via jack or an USB-Device. This renders the audio-system useles as it created a feedbeck-loop.
How I can reconfigure this.
I am attempting to write a small helper app for macOS that captures the input of a Nimbus Steel Series game controller and converts it to keyboard and mouse events for another application (a game that does not support controllers).
In my first attempt I used GCController but as soon as the app becomes inactive no more events are received from the controller. There seems to be no way to change this.
In my second attempt I used CBCentralManager to discover the controller, hoping I could work with it using standard Bluetooth services. But the controller does not even show up in a scan, either with the controller being connected or disconnected. I find devices around the house (iPads, iPhones, smart tv's, computers), but no peripheral that identifies itself as Nimbus. However, there are a couple nil peripherals which I suppose are auxiliary peripherals from Apple devices such as the Magic Mouse or the Wireless Keyboard.
In my third attempt I tried to make the main window an NSPanel in HUD style. The panel stays afloat but it still becomes inactive when I click elsewhere. No controller events received. I thought maybe I could show the panel above the fullscreen game in a corner somehow. But it still needs to be active to get GCController events, then the game would not get events.
Are there any other options to receive game controller inputs which the app is inactive?
Would it work via IOKit? I have been hesitant to use IOKit so far because I was hoping to resolve this issue without it, being a very lowlevel API.
I solved this problem using the IOHIDManager functions. The callbacks receive events even if the app is not active.
I'm currently doing a test UWP app, the goal would be to put this on a Raspberry PI with Win 10 IOT ont it.
I've not much content, the application just display all the zodiac signs, and when one signed is clicked, it displays the current sign information. This will be display on a monitor here. So I would like to be able to navigate between sign, with a remote by example(but I'm open to any other proposal).
What would be the more adequate to navigate on the application(knowing that I don't need to enter anything, that it's not a touch screen but a simple monitor).
Thank you
You could use the GPIO port on the Raspberry Pi to connect the device with any of external controllers of your choice. Wired buttons would be pretty simple, and for a remote your could use an infrared receiver. The GPIO allows you to interact with pretty much anything electronic so the possibilities are pretty much endless.
For interacting with the GPIO port you need to add a reference to the "Windows IoT Extension SDK" to your universal windows app project.
The samples repository has code examples on how to interact with the GPIO port, and many of them are explained with tutorials.
Recently I was experimenting with controlling my Raspberry Pi's HDMI screen using libcec. I made a few settings changes (which regrettably I didn't keep track of), and when I re-booted the Pi, I got a blank screen.
This now happens every time I boot the Pi normally. I see a few boot messages and then the screen abruptly goes black (before I'm given the option of logging in). The only way I can access the command line is if I add "init=/bin/sh" to cmdline.txt.
What I'd like to do is undo the changes and return the Pi's HDMI settings back to normal. Is there a simple way to do a total reset of libcec / cec-client? Do I need to uninstall libcec? If so, how do I do that?