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

[Suggestion] Change ASP request layout #531

Open
DotWallop opened this issue Jan 5, 2025 · 7 comments
Open

[Suggestion] Change ASP request layout #531

DotWallop opened this issue Jan 5, 2025 · 7 comments

Comments

@DotWallop
Copy link

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:
image

I request that we incorporate the same design as this for our ASP selection menu.

@Adrian2k
Copy link
Collaborator

Adrian2k commented Jan 5, 2025

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)?

@Adrian2k
Copy link
Collaborator

Adrian2k commented Jan 5, 2025

It seems like this is dependend on which setup we use, type A or B.

From type A Manual:
image

Type B manual:
image

@Adrian2k
Copy link
Collaborator

Adrian2k commented Jan 5, 2025

@morettio I know there was a reason why we use type A, but I can not remember what this reason was.

@Adrian2k Adrian2k moved this from Unassigned to Suggestion for review in ENOR Sectorfile Jan 5, 2025
@morettio
Copy link
Collaborator

morettio commented Jan 5, 2025

One reason was that the Release tag function on type B was in a sub-menu, not on type A.

@DotWallop
Copy link
Author

No clue what A and B types are, but is that something we can request for whatever type we're on, then?

@morettio
Copy link
Collaborator

We will not change to the other type, Some things won't work and need to be changed and added to make it work.

@DotWallop
Copy link
Author

DotWallop commented Jan 10, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Suggestion for review
Development

No branches or pull requests

3 participants