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
Empty plugin toolbar actions (chat/groupchat) #563
Comments
@Neustradamus You should write Psi+ version in such bug reports. |
@tehnick: Your last build :) |
@Neustradamus
Such useless messages from you (plus their huge amount) already caused to that some developers stopped reading emails from GitHub (at least for activity in Psi/Psi+ projects). |
@tehnick: 1.4.1275 (2020-05-21, Psi:8ce049f8, Psi+:2170e90) Because they think that there is no problem, but maybe they do not use this XMPP client :) |
I have found that this bug was introduced in Psi+ 1.4.1237: This commit broke toolbar settings: |
Fixed in Psi+ 1.4.1303 and newer. |
@Ri0n, @tehnick: Thanks but it is not solved and it bugs a lot! Before the empty bug:
Currently: You can test with Chess / Gomoku / OMEMO / OTR / etc. |
Before changing mechanism of receiving of meta-information from plugins. The main idea was: do not load+unload unused plugins for this, but read meta-information from plugin files instead.
Yep, this was convenient. @Ri0n could it be done with current architecture?
No comments...
Yes, this is a one more regression. And serious one. @Neustradamus |
toolbar buttons for disabled plugins are rather confusing than convenient. |
Then at least:
|
I had forgotten and I have edited:
|
As I said it's kind of confusing to add kind of not existing stuff on the toolbar. Even so already added items are not removed now and therefore error-prone
fixed
fixed
see 1. "error-prone"
in progress
not reproducible |
I'll open another task for 5. everything else if fixed |
no idea. I tested with the latest version with two different profiles and it worked perfectly |
Empty plugin toolbar actions (chat/groupchat):
The text was updated successfully, but these errors were encountered: