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

Feature Request: TotalLength in desc_fs_configuration #2

Open
AmeNote-Michael opened this issue Nov 4, 2023 · 2 comments
Open

Feature Request: TotalLength in desc_fs_configuration #2

AmeNote-Michael opened this issue Nov 4, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@AmeNote-Michael
Copy link

Can the TotalLength be based on a #define variable like desc_fs_configuration_length.

Then desc_fs_configuration_length could be based on further defines like:

#define desc_cdc_length xx
#define desc_midi1_length yy
#define desc_midi2_length zz

#define desc_fs_configuration_length desc_cdc_length + desc_midi1_length + desc_midi2_length

@starfishmod
Copy link
Member

Can you explain the reason this is wanted?

@AmeNote-Michael
Copy link
Author

Can you explain the reason this is wanted?

We are being arrogant assuming that we are the only items in a full descriptor - and if anyone wants to "include" these descriptors into their own offering, it would be nice for them to just edit parameters instead of direct hex output.

For example, one project I have I use a jumper to determine if adding PicoProbe or not - I needed to figure out where sizes were and then create my own parameters to use. Thus I think it would be best to have as a parameter.

@starfishmod starfishmod added the enhancement New feature or request label Dec 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants