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

Enhancement: Improve input types for instance parameters #1227

Open
HugoBDesigner opened this issue Sep 10, 2024 · 0 comments
Open

Enhancement: Improve input types for instance parameters #1227

HugoBDesigner opened this issue Sep 10, 2024 · 0 comments
Labels
Type: Enhancement This is something that improves upon an already existing thing.

Comments

@HugoBDesigner
Copy link
Member

What would this enhancement be for?

Hammer

Describe your enhancement suggestion in more detail

When using the func_instance_parms entity, you can pick an input type based on FGD input types. This allows for users to define the type of parameter they want to receive for a given variable, such as color255 for colors, studio for models, target_name_or_class for entity names, and so on.

The issue arises in that, when you pick an input type, Hammer will only show the appropriate gizmo in the func_instance if you have no default value set for the func_instance_parms variable. For example, setting the parm1 keyvalue to $test angle works and shows up an angle selection gizmo for that variable in the func_instance, but setting it to $test angle 0 or putting anything as the default value completely removes the gizmo.

Ideally, the instance should show you the gizmo no matter what, but also what the default value is. Additionally, input types like choices have currently no way of setting up what the choices should be, so it only works as an empty dropdown. By allowing users to interact with the proper gizmos for a given input type, it'd make mapping with instances – especially complicated ones with multiple variables – significantly easier and clearer for everyone. It'd also be very helpful if you could either set up a custom, visual-only name for a parameter, or at the very least have the contents of the Comments field carry over to the corresponding instance.

@HugoBDesigner HugoBDesigner added the Type: Enhancement This is something that improves upon an already existing thing. label Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement This is something that improves upon an already existing thing.
Projects
None yet
Development

No branches or pull requests

1 participant