Hi @virgil sisoe (virgil89) : could you show us as small snippet how you are loading them into the PreviewCollection (how is the path you are passing into .load() constructed etc.)?
(this might give a hint when this changed)

@Olivier Maury (omaury): I assume this can be closed now? (from reading this, all issues seem to be resolved?)

I'm currently in a bind at work, and this would be tremendously helpful. I need to access Render Result pixels, and the most lightweight way to do so would be to access them directly. Performance is highly critical for the job at hand, and using GPU offscreen techniques proved to be quite inefficient.

Time to close that one I think, further development shall be handled through T63733: Python & Add-ons Module.

@Campbell Barton (campbellbarton): seems related to rB6b0d4302beb5 / rB48e8a1a16701 / rB5ac9e587d48c, mind checking?

Confirmed, checking...

sorry, i guess this isnt really a bug, more of a misunderstanding on my part.

In T68303#747327, @Sybren A. Stüvel (sybren) wrote:

Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.
A guideline for making a good bug report can be found here: https://wiki.blender.org/wiki/Process/Bug_Reports
Marking as "Incomplete" until the requested information/data is provided.

Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

Change info about whitespace trimmed lines from popover to report in statusbar.

@Bastien Montagne (mont29): should we tweak the data-path-reporting to their respective owner then? (or is this this even imposiible? -- havent checked code yet...)
(inclined to repoen as TODO with low prio for my desk -- this has been bugging me as well, just feels like a bug -- same goes for T68054...)

Generating the proper 'python path' is not always working, especially with ugly things like 'root' node trees of other IDs. Thanks for the report, but that's not considered a bug, although enhancements are possible here for sure.

That is not technically a bug, although it is confusing (and a pain to handle in C code as well), 'root' node trees *are not* regular data-blocks, and are not available from bpy.data. They are closer to some private data of their owner (material, light, scene data-blocks), and should only be accessed through them. Thanks for the report anyway.

Will put on my desk for investigation

Can confirm, T68053 is a bit related, will put on my desk for investigation...

Confirmed, checking...

In general this is useful, there is a problem though.

Updated the diff: Using clipboard code has been removed, instead code to get selection by @Dalai Felinto (dfelinto) has been used: https://developer.blender.org/diffusion/BAC/browse/master/text_editor_hastebin.py If/when this function will be added to the API this def can be removed.

Confirmed, checking...

I am not available to look into this this week, so it might not make it into 2.80, but can step down from it, so others can pick it up.
Sorry this has been lying around, other things had higher priority...

@Philipp Oeser (lichtwerk) Any updates on this? Would be nice to get it in for the release.

It seems that this can even result in crash.

I don't know if bpy_traceback.c changed, or if python was updated since 2.79b.

Also If you set the orientation type to VIEW and dont set the orient_matrix, it will use the global orientation.

Fixed by rB366865dd020904116086e6d9ec46b8f70c42cdd1

Before the final release I think this should be fixed. I noticed this bug is still in the release candidate.

Thanks for the report, but you are creating a new scene in your script, you need to pass the new view_layer to the select_set function:
testob.select_set(True, view_layer=scene.view_layers[0])

oh, @Campbell Barton (campbellbarton) was quicker :)

Thx for finding this @Loïc Carr (dimtion), since this is such a small and safe change, I guess it is fine if I commit this...