- User Since
- Mar 24 2017, 4:05 AM (108 w, 6 d)
Wed, Apr 17
Fri, Apr 12
I just tested with a fresh compile from source (at commit rBd1cda823e0a8) and do not get a crash (Windows x64).
Confirmed error with a recent 2.80 Win64 daily build: blender-2.80-009dbc2bc9fb-win64, build# 800
Hi, this bug tracker only covers issues with Blender itself and Blender related projects supplied by the Blender Foundation. Problems with other non Blender related applications, like Source Filmmaker, are not covered on this tracker and should instead be taken to their respective support channels.
Sat, Apr 6
Thu, Apr 4
Tue, Apr 2
Fri, Mar 29
Thu, Mar 28
Mar 18 2019
Mar 14 2019
@Dalai Felinto (dfelinto) I was not sure how to proceed on this one, so I wanted your input. I don't think there has been many changes to the add-ons affected by this commit, so the situation would still be mostly the same as I described in my earlier comment on Feb 2.
Feb 28 2019
Closing as it has been several weeks since this was filed and no additional information has been provided.
Feb 8 2019
Feb 3 2019
Feb 2 2019
After looking over the code some more, I'm not sure of what the best course of action would be on this. None of the options seem ideal. On one hand I can see that the changes in this commit are going to be problematic in many cases, and leaving the commit stand may give the false impression that the code was "corrected". On the other hand, even if the code change is problematic, the new code is still likely to be closer to what would be needed to get these add-ons running in 2.80 than the code that was replaced and rolling this (and rBAd609009748a604c1df2d8babfa4098260666d01a) back does not "unbreak" anything as the old syntax was already broken for 2.80.
Feb 1 2019
rBAd609009748a604c1df2d8babfa4098260666d01a should be tagged with this as well. I'm looking over the commit now.
Jan 30 2019
Jan 29 2019
@Curtis Barclay (ILoveBoobies) : This doesn't sound like a bug. MeasureIt's tool panel "Show/Hide" button is what toggles visibility for the dimensions in the current view, the N Panel's "Delete All" removes them from the object entirely. If you clicked the "Delete All" button, I don't think there is a way you can undo that action so the measurements are restored unless you saved a copy of the scene to a blend file before clicking "Delete All" that you can reload. If you hit "Delete All" you will have to manually re-add measurements to the scene.
Jan 25 2019
Jan 24 2019
Jan 23 2019
Jan 21 2019
Jan 18 2019
My apologies, I thought I removed all the false positives my updater script caught. It looks like the script needs more fine tuning. I will block it from scanning add-ons already updated to 2.80 before running it again just to be on the safe side. I left 2.80 add-ons in originally as the script was finding depreciated code in some of them.
Jan 17 2019
Jan 16 2019
@Jacques Lucke (JacquesLucke) , I think the submission and review process is still fairly close to the older one outlined here. A few guidelines were being reconsidered for 2.8 (like whether or not people would still be required to create wiki pages).
Jan 7 2019
There seems to be some weirdness going on if wiki user's created subpages without a base page.
Dec 30 2018
I wouldn't worry about saving the full edit history. I'm not sure how you could preserve that without a significant increase to the total size and file count of the wiki archive. It might be helpful to see who the last 50 or 100 people that edited the page are (and maybe the first 50 edits), but if someone needed more info than that they could download the wiki data dump.
Dec 4 2018
Nov 19 2018
Oct 22 2018
Sep 3 2018
Jul 19 2018
Jul 5 2018
Jun 20 2018
Which Blender release did you use? I just tried 0a8af46 from builder.blender.org (blender-2.79-0a8af46-win64) and am still able to reproduce this bug. I updated the "steps to reproduce" and added an "Additional details" section to the description with some more info.
Jun 15 2018
I just saw the big wiki changes happened today. Two questions:
May 27 2018
Fixed bad indexing of select_history in modified select_prev, updated benchmark results with code changes
May 21 2018
May 3 2018
Applied with commit:
May 2 2018
Apr 23 2018
Apr 15 2018
Apr 14 2018
@Philipp Oeser (lichtwerk) I was not entirely sure if you were suggesting a rollback or not, but Ako was.
@Philipp Oeser (lichtwerk), I checked and AkoZ was correct, it's a layer management problem. Part of the problem is Blender's weird "view-dependent layers" option. For some reason Blender sets any layers (in "context.space_data.layers") attached to the current view to "False" if you disable the "Scene Layer Lock" option and switch to Local View. That is what prevents any measurements from showing up. I don't think rolling back rBA8ca82b7d or adding a quick fix like:
"if True in bpy.context.space_data.layers do old_behaviour"
are good options as both of those brings back the view layer inconsistency bug which is (IMO) worse than this Global / Local issue.
Apr 13 2018
Which version of MeasureIt? I can't reproduce the bug with MeasureIt 1.7.0 (included with 2.79b). For me the measurements show in both "Local" and "Global" modes (what "Numpad /" toggles).
Apr 6 2018
Mar 12 2018
Jan 25 2018
@Philipp Oeser (lichtwerk) I thought I remembered reading that Python does 1 or 2 additional operations behind the scenes somewhere, but I can't remember the details. I didn't see any significant change in performance with this hastily written test code though, so I say leave the last commit as is. :)
I forgot MeasureIt runs continuously when the add-on is enabled and measurements are set to "Show". That's why I think I originally left this as two separate statements than using boolean logic to join them as I was not sure how Python handled boolean logic behind the scenes.