liamhays
[Feature Request] If a file path is passed when opening an app, have a slight delay and send the "Ok" button
Reading through the source, I saw how a flipper file path can be passed when opening an app to open a file in an app. It logically follows if someone is doing this they want the app to send/play that file.
Eg if you open the subghz app with a file, you probably want to send that file. Not just have the file sitting open ready to send in the subghz app.
Such a feature would allow other interesting possibilities as well, such as "playing" a file without it remaining on the flipper when used with a frontend wrapper. In the background the wrapper could: Send the file to the flipper, open the app with the file as a parameter, "play" the file, then delete the file.
I have such a wrapper, just looking to extend the functionality a bit if you are willing (I don't know rust or I would be trying myself).
I'm definitely not interested in adding major changes like a wrapper. You can probably tell that flipwire is on maintenance mode, and I don't really plan to change that.
As for the OK button concept, give me a bit of time to first find my Flipper and then play with it to see if that's something practical to implement. I don't remember how all the apps work, so if some of them use different buttons than others to execute on a file, that adds a lot of complexity any way you look at it.
I appreciate you looking into it, pretty sure I saw key codes in the protobuf defs.
A function would be ideal so any key could be passed (just make the end user look up the protobuf for the key 😆 ). But simple is fine.
Apologize for the wrapper misunderstanding, I wasn't asking for one, I have already written a simple python one that I use on my linux phone. I was simply thinking about the functionality I could add to my wrapper if I am able to use flipwire to send button presses!