-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Traceback "more" enhancements #6165
Comments
Edited, I think "volume" is a better word than "speed" for the size of each payload |
I believe As for allowing the number of pages sent at a time to be configured (and potentially changing the default of that setting to 2), currently there are 2 There is currently the |
Wouldn't it make sense for Regarding the number of messages change, that makes sense, although one option could be to clamp the length of the most recent message a bit and include "type |
While I can understand the user experience reasoning for adding either of these two features, I'm not sure if the API is really built for either to be a good option. While I'm not ruling out accepting either of them, I personally don't think the benefit to users outweighs the fact that they allow users to override the cog creator's intention of using this method to prevent API spam, somewhat degrading the method's purpose. |
What component of Red (cog, command, API) would you like to see improvements on?
traceback
Describe the enhancement you're suggesting.
Right now, the default UX feels pretty clunky. The feature I proposed was to stop messages from flooding the chat, and it's certainly doing that, but it's also stopping the user from gracefully seeing all messages at once. I'd propose the following enhancements:
all
Of course, replace my fake command with the actual command that changes 2 to the user-set pagination volume.
Anything else?
I really appreciate that you take the time to implement my UX suggestions, and I feel really bad that this one didn't turn out great in its first implementation. I think with these improvements it'll be a much better experience though.
The text was updated successfully, but these errors were encountered: