You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Been messing around on the samples a bit so figured I should have an issue to track these for future integration and better coordination/discussion. My current mess of a branch is here. Plan to clean-up individual features and sample additions in the future once the WinUI/UWP based sample apps are in main.
Add Mouse Input (Movement, and Left Click)
Right Mouse Button
Add Mouse input to pure Win32 sample
Keyboard Input? (Not sure about complexity here and extra value?)
Dynamic Shader Color Parameters
Generalize parameter options that appear for selected shader:
Color Selector button
x to y Float Range thumbs?
Bool toggle button
Use Attributes on Shaders or have sample detect public properties maybe?
Extra Buttons
Quit Button (top-left)
Full Screen Button (left of quit)
Restart Shader Button (left of bottom buttons)
Improved Settings UI (Make toggle to bring up buttons to configure shader parameters)
Other UX Improvements
Add Name of Sample to Shader List
Bug? (Investigating) Shader's Shared in List with texture resources cause degradation...?
ComputeSharp is really cool, so having a wide variety of samples shows folks what's possible with the tool. It also increases the number of converted GLSL shaders which helps provide a better reference for folks familiar with that technology.
Description (optional)
Been messing around on the samples a bit so figured I should have an issue to track these for future integration and better coordination/discussion. My current mess of a branch is here. Plan to clean-up individual features and sample additions in the future once the WinUI/UWP based sample apps are in main.
Rationale
ComputeSharp is really cool, so having a wide variety of samples shows folks what's possible with the tool. It also increases the number of converted GLSL shaders which helps provide a better reference for folks familiar with that technology.
FYI @ahmed605, @Sergio0694
The text was updated successfully, but these errors were encountered: