-
Notifications
You must be signed in to change notification settings - Fork 32
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
The focus on the dropdown list of interpreters that can be started is on the last line .. more useful to have on the first #129
Comments
How about just changing the order in which the interpreters are listed: Version 14.1 Otherwise it all seems a bit upside-down to me. |
The reason for having the list in reverse order was that originally the focus was on the first item of the list, rather than the last. And I would argue that the user is more likely to want to attach RIDE to the highest versioned interpreter.
I appreciate that I am an unusual case, but my list of interpreters on Windows has 7 entries for interpreters that I can attach RIDE to, and 30 that it can’t.
How about suppressing the unusable ones ..
A
From: jayfoad [mailto:notifications@github.com]
Sent: 14 March 2017 09:55
To: Dyalog/ride
Cc: dyaandys; Author
Subject: Re: [Dyalog/ride] The focus on the dropdown list of interpreters that can be started is on the last line .. more useful to have on the first (#129)
How about just changing the order in which the interpreters are listed:
Version 14.1
Version 15.0
Version 16.0
Other... <- default selection is here
Otherwise it all seems a bit upside-down to me.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#129 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AKkCEsofsQp5dkwvvF5794GupE7JncoBks5rlmPxgaJpZM4MbNTO> .Image removed by sender.
|
Right, and with my suggestion the focus would still be right next to the highest versioned interpreter.
That seems like a backward step. We'll get complaints that "I've got APL installed but RIDE can't find it". |
Not hugely fussed about the order .. although I find it more natural to start at the top of a list and work my way down – it is after all a dropdown list rather than a dropup list !
But as long as “Other” is next to the highest versioned interpreter, that’s the important bit.
From: jayfoad [mailto:notifications@github.com]
Sent: 14 March 2017 10:11
To: Dyalog/ride
Cc: dyaandys; Author
Subject: Re: [Dyalog/ride] The focus on the dropdown list of interpreters that can be started is on the last line .. more useful to have on the first (#129)
The reason for having the list in reverse order was that originally the focus was on the first item of the list, rather than the last. And I would argue that the user is more likely to want to attach RIDE to the highest versioned interpreter.
Right, and with my suggestion the focus would still be right next to the highest versioned interpreter.
How about suppressing the unusable ones ..
That seems like a backward step. We'll get complaints that "I've got APL installed but RIDE can't find it".
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#129 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AKkCEt9IFp-ecIW02ArC6GeZ7bpPXqYFks5rlmesgaJpZM4MbNTO> .Image removed by sender.
|
|
It seems odd to me that the focus by default is on "Other" rather than the latest "installed" interpreter, I would expect the focus to be on 16.0 if I have that installed. To me, "Other" would be for advanced users, 90% of the time you're probably going to want the latest APL that is installed on the box. |
The ones it won't work with are greyed out and not selectable, so that's not an issue. How about: Version 16.0 <- default selection is here |
Sorry .. do you mean
Version 16.0 <- default selection is here
Version 15.0
Other…
Version 14.1, 64-bit, Classic (unsupported)
That is that other is between the list of supported and unsupported APLs ? Or that “Other…” still comes at the bottom of the list ?
A
From: jayfoad [mailto:notifications@github.com]
Sent: 14 March 2017 11:38
To: Dyalog/ride
Cc: dyaandys; Author
Subject: Re: [Dyalog/ride] The focus on the dropdown list of interpreters that can be started is on the last line .. more useful to have on the first (#129)
"I've got APL installed but RIDE can't find it" is much better than "RIDE won't work with APL"
The ones it won't work with are greyed out and not selectable, so that's not an issue.
How about:
Version 16.0 <- default selection is here
Version 15.0
Version 14.1
Other...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#129 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AKkCEvNipLei8g125eoXrKvCn2YHNSUmks5rlnwHgaJpZM4MbNTO> .Image removed by sender.
|
Looks good to me. |
I meant what I said: "Other..." at the bottom of the list. Looks a bit odd to me to have it sandwiched in the middle. |
The dropdown list of interpreters which can be started from RIDE is in reverse order - the most recent at the top of the list. This seems sensible.
However, the "Other ..." option is at the bottom of the list, and is where the focus is initally on the dropdown list. Be better to have the focus at the top of the list .. possibly move "Other ..." to the top ?
IDE:
Version: 4.0.2729
Platform: Win32
Date: 2017-03-12 00:25:35 +0100
Git commit: 65c21df
Preferences:{
"favs":"[{"type":"connect","ssh_auth_type":"pass","ssh_tnl_auth_type":"pass","name":"debian7dev","host":"debian7dev.dyalog.bramley","port":"4502"},{"type":"connect","ssh_auth_type":"pass","ssh_tnl_auth_type":"pass","name":"dfsaix","host":"10.0.61.100","port":"9003"},{"ssh_auth_type":"pass","ssh_tnl_auth_type":"pass","name":"mac0","host":"mac0"},{"ssh_auth_type":"pass","ssh_tnl_auth_type":"pass","name":"local","host":"127.0.0.1","port":"9999","type":"start","exe":"C:\\Program Files\\Dyalog\\Dyalog APL-64 16.0 Unicode\\dyalog.exe"},{"ssh_auth_type":"pass","ssh_tnl_auth_type":"pass","name":"p7-61qa","host":"p7-61qa","port":"4503"}]",
"kbdLocale":"en_GB",
"lineNums":"0",
"selectedExe":"C:\Program Files\Dyalog\Dyalog APL-64 16.0 Unicode\dyalog.exe",
"title":"{WSID} {PID}",
"wse":"1",
"zoom":"-2"
}
Interpreter:
Version: unknown
Platform: unknown
Edition: unknown
Date: unknown
The text was updated successfully, but these errors were encountered: