adding a reload feature incase messages not recieved, or out of sync#401
adding a reload feature incase messages not recieved, or out of sync#401justinbaskaran wants to merge 1 commit intoOrangeDrangon:masterfrom
Conversation
|
Why was this closed I am not necessarily opposed to this? |
|
Hey Kyle, I closed it because if you go to View -> Reload it does something similar (this feature would have been a forced reload of the web app on electron), so I guess we could keep it open? what do you think? I think the issue is reload vs forceReload....so once basically forces the electron app to refresh... we could keep it....for usablitiy, we should probably keep one of them, its up to you, though |
|
Sorry for being slow to get back to you. If you find the already existing reload working then yeah we probably do not need this. Let me know if the preexisting button is solving the issues you are running into. |
| { | ||
| label: "Refresh", | ||
| role: "forceReload", | ||
| }, |
There was a problem hiding this comment.
This should probably not be part of the setting menu. If we go with this action type i would prefer to see it in the window menu. It will also need to match the key binds of the already existing refresh, Thanks for the contribution.
So i added a refresh option, so that if users have messages that are out of sync, or not getting messages, they can use this option to force a reload of the web app.....