-
Notifications
You must be signed in to change notification settings - Fork 463
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
"Edit Cmake Cache UI" not working #1591
Comments
I am not able to reproduce as you describe. Everything gets saved properly in all scenarios. |
No popups appear when I press the Save button. Here are the cmake logs:
|
This is still very mysterious because when I press SAVE I see lots more in the output channel. |
I have the same issue. The cache editor appears not to work at all. As described here, the * remains in the editor tab after pressing Save. The popup then asks if I'd like to save again. Subsequently running a configure doesn't include any of the changes. |
@andrewmcdonald-oxb It sounds like the SAVE button is not connected to any handler. You can verify this using the developer tools. While the cache editor is open, please run Furthermore, can you please check if there are any errors logged to the "Console" tab? |
Same problem. It seems that only some of the string options do not work. Here are errors given by
|
This issue is now marked as 'stale' due to there being no activity on it for the past 30 days and being labelled 'more info needed'. Unless the 'stale' label is removed or the issue is commented on, this will be closed in 7 days. If you would like to make this issue exempt from getting stale, please remove the 'more info needed' and 'stale' labels or add the 'stale-exempt' label |
This issue is now closed due to there being no activity on it for the past 7 days since being marked as 'stale'. |
Brief Issue Summary
Changes made with the Cmake Cache UI editor don't get saved.
Expected:
Apparent Behavior:
CMake Tools Log
Developer Tools Log
Platform and Versions
e5a624b788d92b8d34d1392e4c4d9789406efe8f
x64
Other Notes/Information
The text was updated successfully, but these errors were encountered: