Skip to main content
JHans.6
JHans.6
Associate II
July 1, 2021
Solved

STM32CubeIDE 1.6.1 inactive code bug

Not sure where to report this.

I have recently upgraded to OSX Big Sur and also to STM32CubeIDE 1.6.1

Not sure when this issue started, I'm pretty sure it wasn't a problem before, and it does NOT happen on my Eclipse 2020-06 installation.

Restarted, rebooted and reinstalled. No difference.

The issue is that when a file contains inactive code, i.e. marked with #if / #endif, any entering of data BEFORE the #if will "disappear" as long as I type. About 2 seconds after the last keystroke, the entered data will appear. It's not entirely invisible when typing, there are some pixels fluttering at the bottom of where the characters should be.

Entering data AFTER the #endif is no problem.

If there are multiple inactive code blocks in the file, data can only be entered properly after the last one.

This only happens if the code is inactive, with #if 0 as below.

If I make the code active with #if 1, there is no problem.

This happens in ALL my projects in STM32CubeIDE.

And ONLY in files that has any inactive code in them.

Changing the theme (Dark/Classic/Light) makes no difference.

Would be nice to hear if anyone can reproduce this.

And, to get it fixed obviously, it's very annoying.

Edit: I forgot to add, that turning off inactive code highlight in preferences will "fix" the problem.

But that is an emergency workaround. I WANT to see inactive code marked.

//writing here is broken
 
#if 0
#define TEST	1
#endif
 
// writing here is ok

This topic has been closed for replies.
Julien D
Julien DBest answer
ST Employee
July 2, 2021

Using 1.6.1 I'm able to reproduce on Big Sur/M1 but not on Catalina.

However it works perfectly using the inhouse 1.7.0 version (see attached recording), which should be delivered "very soon".

Note that this next release will integrate an update of Eclipse platform (2020-06 -> 2021-03), and Eclipse did quite a lot of work to support Big Sur in this timeframe.

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
View in thread

6 replies

TDK
TDK
July 1, 2021

What do you mean by disappear? Does it get deleted or is it just a visual bug?

Haven't encountered anything like this on Windows.

"If you feel a post has answered your question, please click ""Accept as Solution""."
JHans.6
JHans.6Author
Associate II
July 1, 2021

DIsappear, or rather, the text is not shown while it's bring typed. Only show up 2 seconds after I stop typing.

Have you tried my example?

It's 100% repeatable.

Typing BEFORE the #if 0 is bugged.

Typing AFTER the #endif is ok.

TDK
TDK
July 1, 2021
Yes, works fine for me. I assume it’s a graphics bug specific to Mac.
"If you feel a post has answered your question, please click ""Accept as Solution""."
JHans.6
JHans.6Author
Associate II
July 1, 2021

Here's a recording of the issue

Mac issue or not. This needs to be fixed.

It's NOT an issue when using "regular" Eclipse.

Julien D
Julien DBest answer
ST Employee
July 2, 2021

Using 1.6.1 I'm able to reproduce on Big Sur/M1 but not on Catalina.

However it works perfectly using the inhouse 1.7.0 version (see attached recording), which should be delivered "very soon".

Note that this next release will integrate an update of Eclipse platform (2020-06 -> 2021-03), and Eclipse did quite a lot of work to support Big Sur in this timeframe.

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
JHans.6
JHans.6Author
Associate II
July 2, 2021

Thank you!

That confirms that it DID work fine before. I also was pretty sure I'd never seen it happen on Catalina (or previous).

But I was not sure if it was due to 1.6.1 or Big Sur.

It's not a show-stopper, just pretty annoying, but at least I know a workaround.

Thanks for looking into this, I'll try load up with patience for 1.7.0

Terms & ConditionsAccessibility statement