cgcookie / addon_common Goto Github PK

I am still in the process of trying to figure out the exact criteria for failure but starting to collect thoughts here.

Desired Behavior:
-Have CookieCutter ops be able to go full screen on invoke, taking entire control of the UI for a very structured workflow

Current Attempts:
-Use a separate operator, a "Wizard Start" that calls bpy.ops.screen.screen_full_area() and then calls the first CookieCutter operator>
Fails: rays.py and useractions.py complain about a None types not having atrirbutes "width" etc.

-Call bpy.ops.screen_full_area() in the start() or start_ui() methods
Fails: rays.py and useractions.py complain about a None types not having atrirbutes "width" etc.

File "....\addon_common\common\useractions.py", line 167, in init
self.size = (context.region.width,context.region.height)
AttributeError: 'NoneType' object has no attribute 'width'

I want to use FSM part of cookiecutter, in my commercial addon. It this allowed?

Would it be possible to get the code used in the Bcon18 conference talk? It would be extremely helpful in understanding how to use this framework with a complete working example to work from.

Hi!, i've been trying to create an ui with cookiecutter for some days now, and i wanted to add icons to the buttons (like the options panel in blender, an icon on the left of the button and then the label). But i have been completely unsuccessful. Is this something that should be theoretically possible, or are there any limitations that prevent this? (Im not very skilled on programming yet, it could be something totally stupid that i am missing)

Is it possible to restrict the rendering of the UI to a certain view3D space viewport? For example, if launch a CookieCutter based operator in one of the default workspaces called Animation, which has 2 viewports, the UI is rendered randomly there.

I noticed today that when calling self.done(cancel = True) from within an fsm state (on ESC press) that the operator does not exit unless mouse cursor hovers outside the main UI addon window.

not sure if this is an issue or it was intended this way.

PS: is self.done(cancel = True) more elegant way of exiting the addon altogether than self.done()

[edited by patmo141]

We've had them before. I kind of like this slider bar with no text input.

https://github.com/jayanam/bl_ui_widgets/blob/master/bl_ui_slider.py

These are just my gut feeling when interacting with this

a) boxes should clear when you select them, or start cursor at the end, since you have to delete the old value

b) ability to highlight and delete

c) longer pause so that 2 doesn't become 22222222222222 if your fingers are slow. Maybe even disable whatever that's called.

d) option for slider

I've been experimenting with creating UI with CookieCutter yesterday and I think I found a significant limitation in the way the whole library can be used. It seems to be impossible (just judging from event passing code) to pass any events to Blender UI when a CookieCutter-based operator is running modal.

I see where the limitation is coming from since it was built primarily for Retopoflow and similar tools implementing their own edit modes basically. But since the modal operators in Blender can be run alongside each other it makes it possible to make UI-only operators implementing no real actions (e.g. useful widgets for viewport or something like that, which could stay open when you keep on working using normal Blender features). So, if that functionality is not supported, I propose adding some functionality to have some control over "allowed" areas where events could pass through, making Blender UI functional.

I temporarily changed in the code in cookiecutter.py to pass through all events, and it seems to be not breaking any UI interaction, dragging or whatever. So I suppose, some functionality like that can be added in theory without too much pain?

The lib is using OpenGL shaders version #120 while Blender 2.8 got moved to core profile. Is there any chance rendering can be updated to the core profile as well? Mac OS X has no support for compatibility profile.

Is there a way to hide UI elements like collapsible or a button, or perhaps to delete them from the UI then be able to re-add them again? Thanks

Using the following code
self.ui_outline_container = ui.collection(label="Outline Properties", parent = self.main_menu)
self.ui_outline_container.builder([...])

does not produce a text label within the UI collection container

When typing in integer or float values into UI_Number() elements, 1,3,5,7 etc will pass through and cause navigation changes in the view.

In an older version, in UI_Markdown class had max_size property and later it has been changed to min_size. That's fine I can work with either. Should it have both? I'm sure there are implications on UI_Collapsible, Containers and buttons etc that I don' fully understand.