review by brecht

review by brecht

Confirmed, will have a look...

It is working in cycles rendered viewport and F12.
LookDev et al. is not working for both eevee and cycles (but that is what T57457 is about...)

If this is about Eevee [which I assume] then this a duplicate of T57457

Not 100% sure if we run into trouble with D4061, but at least this is now also merging the keyframes (as in the 'real' Dopesheet)

When you do this you are ending up with 2 keyframes on the same frame.

Confirmed, will have a look...

• Are we talking about 2.79? Or 2.8?
  • (archimesh hasnt been ported to 2.8 afaics)

Confirmed,
@stephen leger (stephen_leger): mind checking on this one?

Well, just noticed that the bone Transform panel is missing as well when pinning a bone. (this should not be the case, right?)
Corresponding panel poll() queries context.object.mode [context.object is None when pinning]

Can confirm, T54133 is related?

Hi everyone, I know this report is quite old, but I think this is fixed in master by a change I made recently (see rB288d7794d4c6836e1322d5ed943c4fbd4b0b0e54)?

review by @Alexander Gavrilov (angavrilov)

Actually (as far as I can see) this addon doesnt provide any functionality that is not builtin already.
Even if you fix the scene.master_collection vs. scene.collection issue you will run into asserts because all operators already exist in blender [now in C] and going further if you fix that as well, you will see that it is the exact same "Collections" panel that we already have...

I have also removed the usage of bbone (as opposed to just bone), as these were the same anyways? [unless I am misunderstanding something here...]

Also getting this constantly printed to the console

col.prop_search(bone, "bbone_custom_handle_start", ob.data, bone_list, text="Custom")
AttributeError: 'NoneType' object has no attribute 'data'

Asserts here
BLI_assert(pchan_index < MEM_allocN_len(pose->chan_array) / sizeof(bPoseChannel *));

Looks like this was crashing in GPU_shader_transform_feedback_enable

Yes, the error message for not finding a string in an enum is truncated to 200 characters:

thanx again for detailed explanantion

I guess this can be considered "Resolved" now?

Confirmed. Will have a look tomorrow.

It is too slow, as a rule we do not do such expensive checks in poll functions. For example the search operator runs thousands of poll functions, and any toolbar with these operators would run it on every UI redraw.

oki, thx for clarifying

might be related to T58671

@William Reynish (billreynish) : not sure if this is off-topic, but could we add multi-object-drag-drop for parenting to the list?
(right now it is possible to multi-object-drag-drop to collections -- but not to other objects [for parenting]... which seems a little inconsistent)

Seems like VIEW3D_HT_header calls
VIEW3D_MT_editor_menus.draw_collapsible(context, layout)

Cannot reproduce.
ALT + left working fine here to select edge loops.

@William Reynish (billreynish) : reg. setting the different context: do you know of an example that does that [when called from a UILayout.operator() -- sorry, seems I am too blind to see atm...]?

reopening for now...

Also could use CTX_wm_operator_poll_msg_set to our advantage here (so lets say when we just grey out the menu entries, we could add this hint to the tooltip, explaining why the menu entry is greyed out...)

As far as I can see the reason for that is that the UI for adjusting the Last operation changed in 2.8 (see T55039, T57731).
In 2.79 it was showing in the 3D View for any command [no matter what editor it was executed in]. I think we all agree this was awkward if you had to have a 3D View open to tweak something you were doing in the UVEditor for example.
In 2.8 this is now done per Editor [Image Editor has it, 3D View has it, probably more to come...]

@William Reynish (billreynish) : yes, thats what I was also worried about

downside: if there are performance costly checks, these would be executed multiple times [e.g. a checking verts_len would be done for both mesh.merge and mesh.remove_doubles in their poll (instead of just once in the menu code)]

I could do a quick check and see how it goes for e.g. checking how many vertices are selected say for 10-15 operators on a fairly highpoly mesh?

it has a hard limit of 0.25, so when you input something negative, it is already clamped to 0.25

I like the idea a lot.
But couldnt we rely on operators poll() more here?
I guess this is what you meant by saying

If we wanted we could have a different kind of poll function where operators can perform more extensive checks, but this seems like it could be over-kill

but I am not sure why this would be a differnt kind of poll? Couldnt all these checks be done in that one existing poll?

This is actually true for all editmode tools.
If you delete an object in editmode from the outliner, the current editmode tool sticks...

Confirmed, will have a look...

This addon is not maintained by blender, so please report the bug to the original author https://github.com/muchasty/Lightmap-Auto-UV/issues

Guess we need a bit more information here:

@Kent Davis (mac4kent) : this report is already closed.
nobody will look at this if you cannot describe what the issue is here.

whatever value I insert in the coefficient for polynomial the animation does not change

Can confirm this is not updating immediately. Muting/Unmuting the (generator) modifier will make it work again...

Not sure what the OS has to do with this issue? (sorry if I am misunderstanding something here...)
[I am on linux btw...]

@Bastien Montagne (mont29): agreed (just thought this was a bit more general in description)

Ah, I see. If you have no objections, I will add Control Points (Segments, too, right?)

Not sure if @Julian Eisel (Severin) has time to look into this?

looks like this is not the case...

Seems like a duplicate of T57655

@Bastien Montagne (mont29): there is also T58856 (and I will merge this report into T58856 -- so this we be off of your desk... of course you could still claim that one if you think this is for you...)

Can confirm a crash [even though a bit different from what the report had as repro steps]:

This is a mixed bag of issues:

The author of that [external] addon is welcome to post this here for review.
But as long as this is not officially supported by blender, well... it is not supported.

We were typing at the same time here, sorry...