| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week. |
Sorry, something went wrong.
|
Pull request closed automatically as inactive. |
Sorry, something went wrong.
|
Pull request closed automatically as inactive. |
Sorry, something went wrong.
|
Pull request closed automatically as inactive. |
Sorry, something went wrong.
Bad bot |
Sorry, something went wrong.
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week. |
Sorry, something went wrong.
|
Please accept this during Hacktoberfest :P |
Sorry, something went wrong.
|
Lol, we need the Lua master here @klutvott123 |
Sorry, something went wrong.
|
just out of curiosity, why is this stalled? any objections? @klutvott123 |
Sorry, something went wrong.
|
@atomgomba It would be nice if they could implement this for the OSD and GPS page as well. 👍 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This is one more step in handling the absence of VTX tables, completely hiding the option in the main menu would make scrolling a tiny bit more convenient and the user won't have to wait a few seconds for no reason just to see "N/A" when clicking on VTX menu.
Also I'm not sure if this is a good solution, I was thinking about potentially being able to hide options for other features as well (e. g. some users might have no GPS or OSD and we could hide those too, or whatever optional feature may come up in the future). Hiding the VTX menu alone would require a simpler logic, hence less new lines added.