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
At the moment I'm looking at trying to get package integrated for uses in mobile apps where we run into an issue and obviously don't have the redux-dev-tools browser plugin to assist. The main issue im trying to work around is that CTRL+H isn't the most accessible key for phones.
My first idea just to get things working for my own uses would be the multi-tap approach where I bind a multi tap or swipe/shake gesture to then send the CTRL+H press. I will update back with any progress I make and if there is any major hurdles for an end-user being able to do this and how it could possibly be upstreamed.
Another path I thought of which could also be nice would allowing the hidden state to show a pullout button/tab in the corner it hides away to that could be tapped to bring it back out and send it back in.
Let me know if anyone has any suggestions for another path I should be taking or if any of my ideas sound good enough to look at as a potential feature/change.
The text was updated successfully, but these errors were encountered:
At the moment I'm looking at trying to get package integrated for uses in mobile apps where we run into an issue and obviously don't have the redux-dev-tools browser plugin to assist. The main issue im trying to work around is that CTRL+H isn't the most accessible key for phones.
My first idea just to get things working for my own uses would be the multi-tap approach where I bind a multi tap or swipe/shake gesture to then send the CTRL+H press. I will update back with any progress I make and if there is any major hurdles for an end-user being able to do this and how it could possibly be upstreamed.
Another path I thought of which could also be nice would allowing the hidden state to show a pullout button/tab in the corner it hides away to that could be tapped to bring it back out and send it back in.
Let me know if anyone has any suggestions for another path I should be taking or if any of my ideas sound good enough to look at as a potential feature/change.
The text was updated successfully, but these errors were encountered: