Cannot open variables from workspace in 2025a/b
245 Ansichten (letzte 30 Tage)
Ältere Kommentare anzeigen
I cannot seem to open variables in the variable viewer in 2025a or 2025b. The behavior is very inconsistent. For some variables, I can initially open them from the workspace by double clicking. A few minutes into my session, I will be unable to open the variables by double clicking. Sometimes when doing this, it will open a variable viewer window and not show anything (either it seems to be stuck on loading the actual content of the variable, or it appears to think it loaded the content without displaying anything). Other times, double clicking a variable does absolutely nothing. It does not work if I right click -> open selection either. When this happens, I CAN see the content of the variables if the variable is accessed through the command window, but this is not the most convenient method for exploring large structs, etc. I've tried reinstalling, regenerating my preferences folder, etc. These did not help. This is super frustrating and makes all 2025 versions largely useless for me.
7 Kommentare
ANDREA
vor etwa 18 Stunden
I found a little workaround: whenever you wanna open a variable, long press it and drag it somewhere else. It should open that variable.
Antworten (2)
James Owen
vor etwa 13 Stunden
There may be 2 separate issues that Gary is experiencing:
- Issues with double click or right click-> open selection sometimes not opening a variable may be the following known issue: If a variable is opened in the Variable Editor and then subsequently closed, the variable with that name cannot then be re-opened in the Variable Editor. Our development team is actively qualifying a fix for this issue now. In the meantime you can work around the issue by copying the content of the variable to a new variable name and then opening that new variable in the Variable Editor. Please check back or set an alert on this post to be made aware of when the fix is available.
- The issue with opening a Variable Editor window which appears stuck or loading. This can happen for some objects which open in a special viewer outside the Variable Editor (e.g. Simulink.Bus). I’m not sure if this applies to Gary’s situation, but if so then the Variable Editor may show a loading spinner in the desktop even though the special object viewer is successfully displayed in a separate window. Our development team are actively qualifying a fix for this issue now as well. If this case applies, the best workaround is just to close the invalid Variable Editor document with the loading spinner
0 Kommentare
Siehe auch
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!