-
Notifications
You must be signed in to change notification settings - Fork 6
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
[Suggestion] Change ASP request layout #531
Comments
Looks much better than how it is done today. I suspect this however has something to do with what topsky setup that is used - A or B. We are currently using version A
Does their sectorfile use COOPANS (version B)? |
@morettio I know there was a reason why we use type A, but I can not remember what this reason was. |
One reason was that the Release tag function on type B was in a sub-menu, not on type A. |
No clue what A and B types are, but is that something we can request for whatever type we're on, then? |
We will not change to the other type, Some things won't work and need to be changed and added to make it work. |
Yeah that I figured, but wouldn’t it be possible to make a feature/dev request to add this layout to our version too?10. jan. 2025 kl. 09:09 skrev morettio ***@***.***>:
We will not change to the other type, Some things won't work and need to be changed and added to make it work.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I find assigning "or less/more" speed restrictions though the current TopSky-tag to be somewhat tedious.
CZQO/EGGX has a layout for this that, in my opinion, is much quicker and fluid than what we have, whilst not taking up too much room:
I request that we incorporate the same design as this for our ASP selection menu.
The text was updated successfully, but these errors were encountered: