Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Add alternating information on the display #24

Open
marc3linho opened this issue Nov 4, 2023 · 3 comments
Open

[FEATURE] Add alternating information on the display #24

marc3linho opened this issue Nov 4, 2023 · 3 comments

Comments

@marc3linho
Copy link
Owner

No description provided.

@groninge01
Copy link

groninge01 commented Nov 11, 2023

I'm going to build one and viewing a dollar or euro price would be nice :)

@marc3linho
Copy link
Owner Author

alternating not implemented

@marc3linho marc3linho reopened this Dec 29, 2023
@jdlcdl
Copy link
Collaborator

jdlcdl commented Dec 29, 2023

I wonder if that rp2.bootsel_button() function can be put to more than just one-time use.

Just throwing some ideas out:

Regarding how many functions that bootsel_button might represent:

  • quick press is interpreted as "next"
  • long press (0.5s to 2s) is interpreted as "previous"
  • super-long press (5s) is interpreted as "leave application mode, go directly to config mode"
    ???

Regarding the "next" and "previous" functionality: maybe it's useful for switching through "modes"?

Perhaps not all modes are interesting, so they could be enabled via checkboxes/multiselect in settings so that user could avoid modes they never want to see?

Perhaps there is a setting for "auto-next-mode" in settings, which represents how long each "mode" should remain on the display. If set to 0 then mode is never changed except via the bootsel_button, else its value could be 30 if they want the mode to change every 30s?

As an example, assuming that a European user only had some modes enabled, "next" might increment as follows:

blockheight, sats per euro, sat-fees
blockheight, sats per euro, euro-fees
blockheight, europrice, sat-fees
blockheight, europrice, euro-fees
blockheight, sats zapped, sat-fees
blockheight, sats zapped, euro-fees
blockheight, euros zapped, sat-fees
blockheight, euros zapped, euro-fees
blocks to halving, sats per euro, sat-fees
blocks to halving, sats per euro, euro-fees
blocks to halving, europrice, sat-fees
blocks to halving, europrice, euro-fees
blocks to halving, sats zapped, sat-fees
blocks to halving, sats zapped, euro-fees
blocks to halving, euros zapped, sat-fees
blocks to halving, euros zapped, euro-fees
blockheight, sats per euro, sat-fees (...and we're back to the first mode)

... while v0.2.0-beta modes would increment as follows:

Block Time, Moscow Time (satsymbol icon), Transaction Fees
Block Time, Moscow Time (sat/USD icon), Transaction Fees
Block Time, Moscow Time (noicon), Transaction Fees
Block Time, Fiat Price ($), Transaction Fees
Block Time, Fiat Price (€), Transaction Fees
Halving Countdown, Moscow Time (satsymbol icon), Transaction Fees
Halving Countdown, Moscow Time (sat/USD icon), Transaction Fees
Halving Countdown, Moscow Time (noicon), Transaction Fees
Halving Countdown, Fiat Price ($), Transaction Fees
Halving Countdown, Fiat Price (€), Transaction Fees
Nostr Zap Counter, Moscow Time (satsymbol icon), Transaction Fees
Nostr Zap Counter, Moscow Time (sat/USD icon), Transaction Fees
Nostr Zap Counter, Moscow Time (noicon), Transaction Fees
Nostr Zap Counter, Fiat Price ($), Transaction Fees
Nostr Zap Counter, Fiat Price (€), Transaction Fees
Block Time, Moscow Time (satsymbol icon), Transaction Fees (...and we're back to the first mode)

???

I'm exploring ideas in a "brainstorm" branch here

...and I've implemented these ideas in a "clicky_dispversion_modes" branch here
however, while I have no waveshare screen at present, would have to remove edits that I made in displayBlockMoscowFees.py where I commented like "#NO_SCREEN_AVAILABLE#".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants