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.

Sign up for GitHub

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

Jump to bottom

Going to the settings option launches Altova XMLSpy 2020 ! #8940

Closed
ghost opened this issue Jan 29, 2021 · 4 comments
Closed

Going to the settings option launches Altova XMLSpy 2020 ! #8940

ghost opened this issue Jan 29, 2021 · 4 comments
Labels
Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-By-Design It's supposed to be this way. Sometimes for compatibility reasons.

Comments

@ghost
Copy link

ghost commented Jan 29, 2021

Hi,
Going to the settings option launches Altova XMLSpy 2020 ! and not the settings.

Thanks
Richard

Environment

Windows 10

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows 10 Pro 20H2 (OS Build 19042.746)

Windows Terminal version (if applicable):
Windows Terminal Preview 1.6.10272.0
Any other software?

Steps to reproduce

Going to the settings option launches Altova XMLSpy 2020 ! and not the settings.

Expected behavior

go to the Settings dialogue

Actual behavior

Altova XMLSpy 2020 is launching
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jan 29, 2021
@zadjii-msft
Copy link
Member

Is Altova XMLSpy 2020 set as you default json editor? Because the Settings button is still going to launch the settings.json file in your default json editor.

@zadjii-msft zadjii-msft added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Jan 29, 2021
@ghost
Copy link
Author

ghost commented Jan 29, 2021

thanks it is, what would it need to be to work as Scott Hanselman demonstrated here ?
Thanks
Richard

Scott Hanselman (@shanselman) tweeted at 7:01 am on Fri, Jan 29, 2021:
Did you get the new Windows Terminal Preview?
🚨THERE IS A SETTINGS UI🚨
https://t.co/2Sww8rXSKJ https://t.co/wgFwHKOagR
(https://twitter.com/shanselman/status/1355048497343459329?s=03)

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Jan 29, 2021
@zadjii-msft
Copy link
Member

From our release notes:

  • IN PREVIEW TODAY: Terminal now has an optional graphical settings editor! Until it's ready for prime time, it's hidden behind a NON-DEFAULT key binding. (Implement the Settings UI #8048)
    • To bind the settings UI to Ctrl+Shift+,, add the following to your keybindings/actions.
{ "command": { "action": "openSettings", "target": "settingsUI" }, "keys": "ctrl+shift+," },
    • The settings editor will become the default action for the Settings menu item and key binding in a future release.
    • Follow along at Epic: Settings UI Completion #6800 for completion stats and community feedback!

@zadjii-msft zadjii-msft added the Resolution-By-Design It's supposed to be this way. Sometimes for compatibility reasons. label Jan 29, 2021
@ghost
Copy link
Author

ghost commented Jan 29, 2021

Thanks that's great.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-By-Design It's supposed to be this way. Sometimes for compatibility reasons.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@zadjii-msft