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
KD4WLE suggested the solution of allowing the administrator to set the default channel that a user is placed into when they login to MeshChat. This avoids people being overwelm by the Everything channel.
The text was updated successfully, but these errors were encountered:
#19 has been progressing, but there are some data synchronization problems. A good amount of problems have been fixed with a Javascript promise to properly load the configuration data from the config API. Now the problem is that the channel select boxes do not get populated until process_messages() gets called well after loading the configuration.
I also fore see future problems with processing messages in the current fashion as the message synchronization gets improved. For the most part the only real way to handle the problem is to create a message class that can handle the DB manipulation and provide a consistent API for the rest of the code to utilize any time a message is being touched.
Contact Details
No response
Enhancement Type
Graphical interface
What is your idea or what can be improved?
Original request for this feature was stated in kn6plv/meshchat#23.
KD4WLE suggested the solution of allowing the administrator to set the default channel that a user is placed into when they login to MeshChat. This avoids people being overwelm by the Everything channel.
The text was updated successfully, but these errors were encountered: