NodeBB 0.9.0 Has Dropped
-
@scottalanmiller said:
Mine doesn't. Often takes up to 30 seconds for it to react and if I do anything I'll end up off of the screen that I was on. Sometimes I forget about it and it pops up for me when I'm doing something completely different. So yours is really fast? Mine varies a lot, but is never exactly instant but probably two seconds when fast, thirty on average and has certainly had times where it was two to five minutes - enough that I was quite surprised when it popped up and had no idea why I had originally hit it.
What version are you on? I had issues like that a few versions ago.
Currently on this version
-
1.2.6 Build 12. I just installed it recently when we were discussing it. It was the latest at the time, I believe.
-
Updated now. 1.2.7 B2 now. So far it pops up instantly. I'll let you know if it turns slow again.
-
@sc
Still getting this. I do not on the nodeBB forum. so I assume it is a setting someplace that may need updated?
Also having an issue getting the names to pop correctly. Going to try and kill my browser in a minute.
I hit @ then s and I see this.
When I hit the c it goes away.
-
I assume that it is this plugin: https://github.com/psychobunny/nodebb-plugin-desktop-notifications
Without it, we don't get desktop notifications, though, which a lot of us rely on. Not sure how to balance that.
-
You could add the concern onto that plugin page directly or make a new thread here only for that issue and I'll link it over to their forum and the plugin's GitHub issue tracker.
-
@scottalanmiller said:
You could add the concern onto that plugin page directly or make a new thread here only for that issue and I'll link it over to their forum and the plugin's GitHub issue tracker.
Thanks for the link. Added an issue to the github for it.
-
Also tagging @psychobunny here so that he can see it.
-
@JaredBusch said:
Also having an issue getting the names to pop correctly. Going to try and kill my browser in a minute.
completely rebooted my machine and still having issues with name auto completion when I need to type one manually.
Edit:
@scottalanmillerIt seem to come and go. that one just worked.
-
I've been having issues with that too. Trying to type in @psychobunny last time did not work at all. This time it worked fine.
-
I would rather have this back at the top:
Flow control is at the top,... so it makes (at least to me) better sense to have it there also.
-
@gjacobse said:
I would rather have this back at the top:
Flow control is at the top,... so it makes (at least to me) better sense to have it there also.
Agreed, this is getting really hard to get used to.
-
@scottalanmiller said:
Updated now. 1.2.7 B2 now. So far it pops up instantly. I'll let you know if it turns slow again.
@JaredBusch it only worked for this long. It's back to the 30+ second delay from when I hit the Print Screen button until it starts its capture.
-
@scottalanmiller said:
@JaredBusch it only worked for this long. It's back to the 30+ second delay from when I hit the Print Screen button until it starts its capture.
I have had it work both fast an slow this morning. I wonder if the issues are plugin related. I know imgur is having issues often lately. Maybe greenshot is making an API call too soon causing the delay if imgur is having an issue. I will test sometime soon by diabling the plugins. probably not today at the rate my morning is going.
-
Oh that's a thought. Imgur is failing on me over and over this morning.
-
@scottalanmiller said:
Oh that's a thought. Imgur is failing on me over and over this morning.
Right. To me, Greenshot should not be making any API calls when you hit the button, but you never know. I have certainly made coding mistakes like that in the past.
-
OMFG quoting is better!!!@!@!@KIO#5^!@^!@$
-
Is the notification.wav notification happening to everyone else still?
-
@coliver not here.
-
nope.
