-
Notifications
You must be signed in to change notification settings - Fork 533
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
skinning example is bad at skinning #286
Comments
Everything is correct here. AFAIK most Nuklear users use the default way of drawing the UI, which does not involve pixel mapped files. As such, no one bothered to include a better skinning demonstration. The current one is sufficient I think for the purposes of explaining skinning functions. Personally, with icons from Font Awesome or Project clarity and a style editor for all the nk_style_XXX options, I never needed to go to pixel mapped skinning to make the UI look good. |
gwen.png is a consistent resolution, its use within the skinning example is not! compare the resolution difference in the screenshot between:
none of these differences are observed in the gwen.png skinning file, and are only correct behavior for a skinned UI by means of parody. furthermore, arguments toward not using a feature are not an argument in defense of a feature. so, example 3 looks pretty good, what's up with 4? |
@floopfloopfloopfloopfloop Now I'm starting to understand what you mean. I will look into the current state of skinning. |
@floopfloopfloopfloopfloop |
The 9-slice PR has been merged in #304. Just in case this was missed. |
Thanks for the work on 9-slice. Any chance there could be a simple example of how to utilize it in comparison to the original skinning method? |
An important point for Nuklear 5.x. I'll push a PR this week addressing styling in it's entirety, including a proposal for a new default style and a file where users may edit the default style elements or change effects like baked soft shadows. All thanks to the awesome 9-slice PR by @Michael-Kelley and @dav64.
I failed to share this, because the style-guide I was porting to Nuklear turned out to be company internal and under NDA. With 5.x it's good timing, because it's something the community can edit collaboratively anyways. |
@floopfloopfloopfloopfloop |
input: running
make
in the example directorycc -std=c99 -pedantic -O2 -o bin/skinning skinning.c -lglfw -lGL -lm -lGLU -lGLEW
output:
The text was updated successfully, but these errors were encountered: