Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shader-picker ui is glitchy with different parameter types #68

Open
StjerneIdioten opened this issue Sep 8, 2020 · 2 comments
Open
Labels
bug Something isn't working

Comments

@StjerneIdioten
Copy link
Owner

Describe the bug
The shader-picker ui looks quite wonky, when the read parameteres have different types like float and float4 next to each other.

Screenshots
image
image

@StjerneIdioten StjerneIdioten added the bug Something isn't working label Sep 8, 2020
@kbrandwijk
Copy link
Contributor

I noticed this as well. A naive approach would be to do what GE does, and just display all of them as float4. I've looked into disabling some of them, but within the FloatVectorProperty control, this isn't possible. Alternatively, a 4 column approach with 4 separate controls could be considered?

What's your desired solution?

@StjerneIdioten
Copy link
Owner Author

I would probably try and avoid making "fake" fields aka the GE way :-P
I think the key lies in playing with the blender UILayout elements, problem is the documentation sucks. I have seen other addons being successful in this kind of thing though, so should be possible.

The shaderpicker was also the first real try I had with manipulating Blenders UI. I believe some of the other UILayout things like split or maybe some form of filler blocks should be able to solve it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants