UI Design on a Denny's Napkin #350
davepl
announced in
Announcements
Replies: 6 comments 1 reply
-
|
I just bought a 64x64 HUB75 display that will provide room for the UI. I think the 64x32 boards should have hidden UI’s above and below the current effect (your scroll break hint, but one on top and bottom). This will allow use of directional arrows on the larger remote. Now, implementing this is a different story! |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Right after I replied to this I realized this was for the web interface… However, I would like to see this on the matrix display! |
Beta Was this translation helpful? Give feedback.
-
|
UI in 64x64px is hard.
See my open bug report on 64line HUB75Es not working. I've been meaning to
build up a board from scratch and see about getting a logic analyzer in
that E line.
…On Mon, Aug 28, 2023, 7:12 PM Andrew Smilie ***@***.***> wrote:
Right after I replied to this I realized this was for the web interface…
However, I would like to see this on the matrix display!
—
Reply to this email directly, view it on GitHub
<#350 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCSD364GG5JDKI2FD7Y773XXUXYFANCNFSM6AAAAAA2DE7H3M>
.
You are receiving this because you are subscribed to this thread.Message
ID:
<PlummersSoftwareLLC/NightDriverStrip/repo-discussions/350/comments/6847590
@github.com>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Interesting. Have you traced the E pin and board visually and see if it
connects to the wrover?
Thanks for the heads up.
On Mon, Aug 28, 2023 at 8:04 PM Robert Lipe ***@***.***>
wrote:
… UI in 64x64px is hard.
See my open bug report on 64line HUB75Es not working. I've been meaning to
build up a board from scratch and see about getting a logic analyzer in
that E line.
On Mon, Aug 28, 2023, 7:12 PM Andrew Smilie ***@***.***>
wrote:
> Right after I replied to this I realized this was for the web interface…
>
> However, I would like to see this on the matrix display!
>
> —
> Reply to this email directly, view it on GitHub
> <
#350 (reply in thread)>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/ACCSD364GG5JDKI2FD7Y773XXUXYFANCNFSM6AAAAAA2DE7H3M>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID:
>
<PlummersSoftwareLLC/NightDriverStrip/repo-discussions/350/comments/6847590
> @github.com>
>
—
Reply to this email directly, view it on GitHub
<#350 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AF2ATVEBBNVVO2IEZSAM6WTXXU53FANCNFSM6AAAAAA2DE7H3M>
.
You are receiving this because you commented.Message ID:
<PlummersSoftwareLLC/NightDriverStrip/repo-discussions/350/comments/6847809
@github.com>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
No. Multi-layer PCB + Uncertainty what pin on WROVER _any_ of the HUB75
pins are connected to. I haven't yet found a declaration or mapping of the
HUB75 pins like we have for LED_PINn and friends. Have you sussed that out?
I know there's _something_ more required than just plugging in a tall
panel. Doubling the number of pixels we're required to shove around may be
entertaining, too.
P.S. My gmail address is the same as my name here.
On Mon, Aug 28, 2023 at 8:47 PM Andrew Smilie ***@***.***>
wrote:
… Interesting. Have you traced the E pin and board visually and see if it
connects to the wrover?
Thanks for the heads up.
On Mon, Aug 28, 2023 at 8:04 PM Robert Lipe ***@***.***>
wrote:
> UI in 64x64px is hard.
>
> See my open bug report on 64line HUB75Es not working. I've been meaning
to
> build up a board from scratch and see about getting a logic analyzer in
> that E line.
>
> On Mon, Aug 28, 2023, 7:12 PM Andrew Smilie ***@***.***>
> wrote:
>
> > Right after I replied to this I realized this was for the web
interface…
> >
> > However, I would like to see this on the matrix display!
> >
> > —
> > Reply to this email directly, view it on GitHub
> > <
>
#350 (reply in thread)>,
>
> > or unsubscribe
> > <
>
https://github.com/notifications/unsubscribe-auth/ACCSD364GG5JDKI2FD7Y773XXUXYFANCNFSM6AAAAAA2DE7H3M>
>
> > .
> > You are receiving this because you are subscribed to this
thread.Message
> > ID:
> >
>
<PlummersSoftwareLLC/NightDriverStrip/repo-discussions/350/comments/6847590
> > @github.com>
> >
>
> —
> Reply to this email directly, view it on GitHub
> <
#350 (comment)>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AF2ATVEBBNVVO2IEZSAM6WTXXU53FANCNFSM6AAAAAA2DE7H3M>
> .
> You are receiving this because you commented.Message ID:
>
<PlummersSoftwareLLC/NightDriverStrip/repo-discussions/350/comments/6847809
> @github.com>
>
—
Reply to this email directly, view it on GitHub
<#350 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCSD32VEJG3UQGJSIYLJZ3XXVC3VANCNFSM6AAAAAA2DE7H3M>
.
You are receiving this because you commented.Message ID:
<PlummersSoftwareLLC/NightDriverStrip/repo-discussions/350/comments/6848013
@github.com>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Is this what you’re looking for? It’s in MatrixHardware_ESP32_Custom.h as required by the SmartMatrix package.
#define R1_PIN GPIO_NUM_2
#define G1_PIN GPIO_NUM_0
#define B1_PIN GPIO_NUM_32
#define R2_PIN GPIO_NUM_25
#define G2_PIN GPIO_NUM_33
#define B2_PIN GPIO_NUM_27
#define A_PIN GPIO_NUM_5
#define B_PIN GPIO_NUM_4
#define C_PIN GPIO_NUM_19
#define D_PIN GPIO_NUM_18
#define E_PIN GPIO_NUM_26
#define LAT_PIN GPIO_NUM_21
#define OE_PIN GPIO_NUM_23
#define CLK_PIN GPIO_NUM_22
… On Aug 28, 2023, at 8:05 PM, Robert Lipe ***@***.***> wrote:
No. Multi-layer PCB + Uncertainty what pin on WROVER _any_ of the HUB75
pins are connected to. I haven't yet found a declaration or mapping of the
HUB75 pins like we have for LED_PINn and friends. Have you sussed that out?
I know there's _something_ more required than just plugging in a tall
panel. Doubling the number of pixels we're required to shove around may be
entertaining, too.
P.S. My gmail address is the same as my name here.
On Mon, Aug 28, 2023 at 8:47 PM Andrew Smilie ***@***.***>
wrote:
> Interesting. Have you traced the E pin and board visually and see if it
> connects to the wrover?
>
> Thanks for the heads up.
>
> On Mon, Aug 28, 2023 at 8:04 PM Robert Lipe ***@***.***>
> wrote:
>
> > UI in 64x64px is hard.
> >
> > See my open bug report on 64line HUB75Es not working. I've been meaning
> to
> > build up a board from scratch and see about getting a logic analyzer in
> > that E line.
> >
> > On Mon, Aug 28, 2023, 7:12 PM Andrew Smilie ***@***.***>
> > wrote:
> >
> > > Right after I replied to this I realized this was for the web
> interface…
> > >
> > > However, I would like to see this on the matrix display!
> > >
> > > —
> > > Reply to this email directly, view it on GitHub
> > > <
> >
> #350 (reply in thread)>,
>
> >
> > > or unsubscribe
> > > <
> >
> https://github.com/notifications/unsubscribe-auth/ACCSD364GG5JDKI2FD7Y773XXUXYFANCNFSM6AAAAAA2DE7H3M>
>
> >
> > > .
> > > You are receiving this because you are subscribed to this
> thread.Message
> > > ID:
> > >
> >
> <PlummersSoftwareLLC/NightDriverStrip/repo-discussions/350/comments/6847590
> > > @github.com>
> > >
> >
> > —
> > Reply to this email directly, view it on GitHub
> > <
> #350 (comment)>,
>
> > or unsubscribe
> > <
> https://github.com/notifications/unsubscribe-auth/AF2ATVEBBNVVO2IEZSAM6WTXXU53FANCNFSM6AAAAAA2DE7H3M>
>
> > .
> > You are receiving this because you commented.Message ID:
> >
> <PlummersSoftwareLLC/NightDriverStrip/repo-discussions/350/comments/6847809
> > @github.com>
> >
>
> —
> Reply to this email directly, view it on GitHub
> <#350 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ACCSD32VEJG3UQGJSIYLJZ3XXVC3VANCNFSM6AAAAAA2DE7H3M>
> .
> You are receiving this because you commented.Message ID:
> <PlummersSoftwareLLC/NightDriverStrip/repo-discussions/350/comments/6848013
> @github.com>
>
—
Reply to this email directly, view it on GitHub <#350 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA4HCF3UDQ3YC5SBM62AEELXXVMBHANCNFSM6AAAAAA2DE7H3M>.
You are receiving this because you authored the thread.
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Yes, Dave. That's helpful. Thank you. My indexer hadn't picked it up as it's the only uppercase filename in the project. Oops. Was that maybe ...75_64ROW_... in your earlier successful tests? It'll probably be Tuesday before I can come back to that... |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I wanted to provide some brief direction for the UI effort, as it looks like it's caught up with the meager directions provided!
Hopefully you can make some sense from this!
I'd like to see all effects in a vertical stack column, as I believe was the case in the most recent.
In this sketch, you'll find the following:
These remain onscreen and do not scroll, but everything below it scrolls as a list. On a wide display like a monitor hosting an HTML page, these should be constrained in width to something visually appealing.
Each effect has an entry here. Effects can be dragged to reorder. The settings page for an effect (TBD) includes a Duplicate Effect and Remove Effect options. Only copies can be removed, not the original built in effect. The intent here is you could copy an effect twice and adjust the settings differently for all three copies.
On the far left of the effect entry is an enable/disable slider. At least one effect must be active, so an error message should tell the user that if they try to disable the last effect. The effect title is left justified against the slider. The settings icon and play button are right-justified. The currently playing effect should light up the play button, others show it in dim green.
Clicking on the effects settings icon takes you to the settings page for that effect (TBD).
Beta Was this translation helpful? Give feedback.
All reactions