If you tried to do the automatic update, it often doesn’t work. Try clicking the link from the first post and then update to the version 0.14.
It should loo like that:
2 Likes
i clicked the 1st post link, lol.
1 Like
Any errors in the console?
Also, did you try to Ctrl+F5 or Ctrl+R refresh the page?
1 Like
yep did both F5 and ctrl+F5 after deleting cache from chrome settings, still nada, here’s a paste of the F12 errors:
1 Like
Ok, thanks for the drop. Unfortunately, none of these errors are from any of my scripts.
I guess, I have to look through the code and think, what could go wrong.
1 Like
says: Utilities 0.14 35 KB in dashboard so i am updated (checked just in case), thanks anyways! 
1 Like
Ok, I think, I might know, where the problem is. For now, try to go to the Options (in the Dock) and deselect then reselect an option named “Display number of segments”.
1 Like
that worked!
1 Like
hehe 
1 Like
nice
1 Like
only suggestion i have is, if easy to implement, to make it white instead of grey, kinda difficult to read it against the black background, thank you regardless!
1 Like
v 0.14.2
Fixed the issue, that the feature wasn’t displayed at first.
Changed the color to white.
After a while - fixed an issue, that when showing neuropils, the counter was disappearing.
1 Like
v 0.14.3
Edit:
Warning: There are some issues with selecting and deselecting segments. I’m working on it.
Edit2: I think, I found the problem and resolved it, but I’ll test it a little bit more this time, before releasing it.
Edit3: Hopefully fixed.
1 Like
it says downgrade instead of update?
1 Like
Yes, I’ve reverted the changes to v 0.14.2, but still have some issues. Still working on it.
Edit: I also have to revert the Dock, because there was the problem. When I fix it, I will push the changes both there and here.
1 Like
Ok, third time’s a charm.
So, in v. 0.14.3.1 I’ve hopefully fixed a long standing bug.
The bug was, that if you clicked the button to show neuropils or do other operation, which restores state (e.g. Presets addon), then some functionalites were no longer working. The functionalities are: delete annotation point (ctrl + right-click to delete an annotation point), delete split point (ctrl + right-click to delete a red/blue split point), jump to segment button (ctrl + right-click on a segment in 2D or 3D to scroll into view and highlight its button in the right panel).
The problem was because I thought, that when restoring a state, only the tabs in the right panel were being recreated. I was wrong - the main tabs are also recreated, so any functionalities assigned to them were being removed.
2 Likes
v. 0.14.4
This one should resolve an issue, that after opening some segments in a new tab, there were problems with opening new ones (localStorage was getting full). Thanks @Celia_D for reporting.
It might require some further clean up in the localStorage in the future (which I will do by this script, you don’t have to worry about it), but for now, the solution in this version should be enough to make things work.
3 Likes
I wonder, would it be feasible (or even desirable?) to have the/a script auto-update a segment that’s selected but lightbulb’s black? So instead of having a player (or admin/researcher?) double click the seg out then in again the script does it automatically. Then again it (script) would have to be scanning all selected segments real time or every # secs/mins which i imagine isnt the best idea possible for burdening the API lol, unless its not done auto but at the press of a button? have a button u press it script scans segments list, updates any/all black ones.
1 Like
i do not think doing it on auto is a good idea, i think it is informative to know a segment have been changed, show you someone else is also working in the same area as you, or even the same cell.
But having a button that update every black lightbulb would be good.
The only trouble i see with this is in case of mergers, what segment should you update it too? so far as i know the ai have no way of knowing what part is the good one and what part is the bad. Could it be possible to add all segments that have been splitt of instead of just updating one segment?
2 Likes
in case of mergers maybe it could pull all new segments (ie if there’s 2 cbs merged pull the 2 new segments)? but then again that’d be bad then someone breaks off a twig from another segment the script pulls both up. Maybe the better idea is to pull the segment that is still attached to the original segment? ie if a twig is severed from a cell (merger) then the script pulls the CB b/c the twig is no longer connected to the ‘starting’ (selected) segment?
1 Like