Opening and closing IDE a few times seems to nuke the project

[adam_C]

Created a number of files in your glorious new IDE.

After opening and closing a few projects in at attempt to find a hidden menu option, I can now see my .project files in finder but attempting to open them with the IDE via double clicking shows NO project data, just a blank space where the explorer should be.

Is this a design 'quirk' with an odd workaround where I can recover the file somehow?

is it an issue with V2.0.0 which needs resolving?

Or is it just an inevitable fact of dealing with this buggy rubbish software?

I actually wouldn't have minded MX moving to a different platform if it was designed to move the whole stack away from this eclipse junk, but I don't understand why you'd expend effort making IDE and MX less usable whilst not bothering to do anything about the buggy or just plain weird behaviour of the IDE

[Ghofrane GSOURI]

Hello @adam_C 

Thank you for posting 

Could you please share a screenshot or a little video that illustrate this behavior ?

Also could you please provide more details about your OS?

Meanwhile I am checking this behavior. I will get back to you asap

THX

Ghofrane

[Andrew Neil]

---

@adam_C wrote:

move the whole stack away from this eclipse junk, 

---

That's what the STM32CubeIDE for Visual Studio Code (MCUs) is all about...

[adam_C]

Hi Ghofrane,

No screen shot, it is just an empty explorer.

Think it was triggered by reindexing in at attempt to change float
behaviour.

After that all the projects that were in explorer have disappeared and
actually when I try to launch a new project from a clean ioc file, I can
see a few onscreen errors show up very quickly and the explorer doesn't
come up again.

So in short reindexing seems to destroy the whole IDE (database) and make
it inoperable.

I do still have my .c and .h files so it is the IDE explore itself which is
broken.

I also don't know if its related to the *** behaviour where MX is one
folder and workspace is a different folder and it seems impossible to get
the new project to run in workspace (due to the *** UI) so new projects
are in Documents / MX instead of workspace

[adam_C]

Thanks, is *STM32CubeIDE for Visual Studio Code (MCUs)
<>*
actually usable / stable?

I know that's a very low bar ...

[Ozone]

Well, it seems for quite some time that the Mac platform is the red-haired stepchild of ST's software department.

But to be honest, Macs are an exotic occurence in the embedded software business. I never came across one in a professional environment.

[TDK]

I have to wonder what is going on inside MacOS (and Linux) that these issues keep happening. Eclipse has been around for quite a while. This isn't something special that ST is doing. What are they changing between versions that is causing stuff to break?

[adam_C]

I'm actually on windows 10 LTSC IoT which should be about as bomb proof as
you can get ...

Planning on going over to VS Code and PlatformIO (using MX for pinout) and
hopefully avoid as much lazy fragile STM software as possible. maybe STM
VS Code plug in at a pinch but the people behind the current mess of an IDE
don't give me confidence that their VS code plugin will be any better

[Ghofrane GSOURI]

Hello @adam_C 

Could you please clarify whether you are keeping your IDE open and simply opening or closing the project, or if you are actually restarting CubeIDE? Also, could you try opening CubeIDE in a new workspace to see if you encounter the same issue?

THX

Ghofrane