You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the calling side it is usually useful to have access to whatever size the display is. In the Scenic driver I'm already expected to provide that information so it ends up a bit redundant. But it seems like if you pass :phat to the start_link if you could get {:ok, pid, display} it would help.
What do you think?
The text was updated successfully, but these errors were encountered:
Changing start_link this way would make it behave in a non-standard way, which could lead to confusion. I can see the value of being able to query an Inky process to see what type of display it's been set to run for, though, and having Inky.Display expose functionality to inspect the type once it's up and running... So I guess I'm just ➕ your comment, hehe :)
On the calling side it is usually useful to have access to whatever size the display is. In the Scenic driver I'm already expected to provide that information so it ends up a bit redundant. But it seems like if you pass :phat to the start_link if you could get
{:ok, pid, display}
it would help.What do you think?
The text was updated successfully, but these errors were encountered: