Unable to save settings

[dotanchase]

I am trying to change the settings in the Approve section. I unchecked some of the features, but the save button is not enabled. I cannot save the selection. What is wrong, and how to enable that?

[RSO]

Hey @dotanchase, I'm currently investigating another issue with the settings window, and am wondering if they're somehow related. Could you maybe tell me what happens if you click on the settings icon (to open the settings window), and then click on the + icon (without trying to make any changes)?

I'm wondering if a dialog shows up that tells you that there are unsaved changes.

[dotanchase]

Which + sign, the one that create a new task or the one that create a new configuration profile? Clicking on the top one (new task), just clears the windows. Clicking on a new profile - it opens a new windows asking for profile name. Sent with Spark

…

On May 20, 2025, 4:00 PM +0300, Remon Oldenbeuving ***@***.***>, wrote: Hey @dotanchase, I'm currently investigating another issue with the settings window, and am wondering if they're somehow related. Could you maybe tell me what happens if you click on the settings icon (to open the settings window), and then click on the + icon (without trying to make any changes)? I'm wondering if a dialog shows up that tells you that there are unsaved changes. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[RSO]

I meant the one to create a new task, but then it seems that you have a different issue. I'll look into it!

[dotanchase]

In my case, this is the SAVE button, it is not enabled. I cannot save the settings. Someone in another forum said that I need to clear the VS Code cache. I did that, but still no help. Sent with Spark

…

On May 20, 2025, 4:16 PM +0300, Remon Oldenbeuving ***@***.***>, wrote: I meant the one to create a new task, but then it seems that you have a different issue. I'll look into it! — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[RSO]

Thanks! I was wondering if you maybe could check if there's any meaningful error shown in the VS Code console. You can open the developer panel through the command pallette, and then check the Console tab:

[HadesArchitect]

Hey @dotanchase, there is already an issue WiP 🚧 regarding it: #439

Thank you so much for the report! I'll update the team on your findings. Please send me your email (here or on discord), I'll send you a little apology tokens 😅

I'm closing this as a duplicate.

[dotanchase]

My email is ***@***.*** Thanks

…

On Tue, May 20, 2025, 16:25 Aleks Volochnev ***@***.***> wrote: Hey @dotanchase <https://github.com/dotanchase>, there is already an issue WiP 🚧 regarding it: #439 <#439> Thank you so much for the report! I'll update the team on your findings. Please send me your email (here or on discord), I'll send you a little apology tokens 😅 I'm closing this as a duplicate. — Reply to this email directly, view it on GitHub <#438 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BN6HQVEYHWGS5R3HKIGGY7327MULHAVCNFSM6AAAAAB5QIOEUGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMRQG4YDQNY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[RSO]

I've reopened this discussion as it seems to be a different one from #439