Page MenuHome

Material Library VX - Add Active Material to library disfunctional
Closed, ResolvedPublic

Description

System Information
Operating system and graphics card

Windows 7 64 Bit, Nvidia GTX 1060

Blender Version
Broken: (example: 2.69.7 4b206af, see splash screen)
Worked: (optional)

2.79b

Short description of error

Clicking at the Add Active Material to library button in the Material Library VX addon is disfunctional. The status bar tells me that the material is added. But nothing happens.

Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps

Activate the Materials Library VX addon. Create a new material. Doesn't matter if BI or Cycles. Go to the addon. Click at the Add Active Material to library button. Have a look if anything arrives. Here nothing happens. What i get is some messages in the console. Which tells me about not found paths and that the material is added ...

The Material Library VX Addon is included in Blender.

Details

Type
Bug

Event Timeline

Not found path message is related to "user defined path" to library not set in addon preferences. It is only info and can't be the source of any error.

By default the addon seek for library in addon folder - when setup into blender addon folder you may facing with "read only" folder issue leading to write into library error.
Properly setting a "user defined path" into addon preferences to a writable folder allow to overcome this known issue - see matlib_vx thread on blenderartists.org as reference.

Thanks for the idea stephen, but it's not a rights issue. The folder is writable. I have meanwhile found out what it is. You can't add a material as long as the filter categories button is active. The way it works is:

  • Turn filter categories off
  • Save Blend file
  • Insert selected Material
  • Select material in the addon list
  • Turn on filter categories and switch to the category where you want to insert it
  • Click at arrow button
  • Refresh Library

And then the new material should be in the category where you want it to be. And is saved in the addon.

So the original error is solved meanwhile, it works as designed. Even when the design is a bit more complicated. < The only thing that i could suggest is to add more descriptions to the tooltips. Or maybe a help text in the addon panel in the user preferences. Or both.

But at the step to click at the arrow button i stumbled across another problem meanwhile. When i turn the library on, and then click at the arrow button, then i get a error message.

Philipp Oeser (lichtwerk) triaged this task as Confirmed, Medium priority.

Even though the first issue seems fixed I can confirm the second ('xml is not defined')

This seems like outdated code (had a quick look at it, but there is also seemingly other outdated stuff flying around, e.g. current_library.materials, ...)

@stephen leger (stephen_leger): mind having a look? Otherwise I'm tempted to just remove that code path (but havent looked in depth)...

Missing proper xml import
Never checked category stuff, i only made some cosmetic changes during 2.79 release process related to user defined library path and fixed temporary scripts path to writable folder.
Will probably require more in depth investigations of overall code, might take a look next week.

@stephen leger (stephen_leger): ok, I have a fix, will push tomorrow...

Philipp Oeser (lichtwerk) closed this task as Resolved.Apr 19 2018, 9:52 AM

regarding the xml error: I pushed rBA8d3301f66c77e7b5a1f310 now.
Closing the whole report as resolved then.

Sorry for resurrecting this thread. I have compiled the newest Blender version, and stumbled across that the fix has introduced a few error messages now at switching the libraries. The version included in 2.79b doesn't show this behaviour.

Warning: 'matlib.libs_menu' doesn't contain '_MT_' with prefix & suffix
Warning: 'matlib.cats_menu' doesn't contain '_MT_' with prefix & suffix
Warning: 'matlibvxPanel' doesn't contain '_PT_' with prefix & suffix

This warning is not related to that fix, it was introduced in master in rB0bbae3f3f659 and rB94b7bf3ec21b [which is not part of official 2.79x releases afaik] and just tells addon devs that bpy types such as menus, panels etc. should follow a strict naming convention [which obviously a lot of existing addons dont do...]

Ah, i see. Many thanks :)

This three error messages comes by the way from this addon :)