IDE Version 2.0.0 - why remove MX ?

[jcslb]

Why, oh why have you separated IDE and MX such that .ioc files can no longer be opened in IDE?

I cannot imagine any benefits and it makes the IDE significantly worse, such that I've felt compelled to revert to version 1.19.0 ( go to Help -> About STM32CubeIDE -> Installation Details -> Installation History -> select version -> Revert)

I couldn't find any other means of feeding back my strong dislike of this change other than a post like this. I hope version 2.1.0 comes out soon and re-integrates MX and IDE!

[samsio_innovations]

Dear ST,

You were known as a standalone provider in the industry that offered a single tool (until STM32CubeIDE 1.9.0) capable of handling MCU configuration, IDE functionality, debugging, and everything else in one place. Developers chose your platform because of its simple and easy-to-use development environment.

Sorry to say this, but the development environment now feels unnecessarily fragmented. Separating the tools, confusing users, and making the setup process more complicated has taken away the simplicity that developers appreciated. We are now forced to spend time debugging the environment setup itself, similar to experiences with other suppliers.

You really need to reconsider these changes and bring back the simplicity that made STM32 development so popular. Otherwise, you risk losing the trust and appreciation you built with developers over the years.

Please rethink this before it is too late.

[Pavel A.]

@samsio_innovations  CubeIDE branch 1.x, with integrated MX still is available and supports majority of STM32 products. Just keep using it?

[mattias norlander]

---

@samsio_innovations wrote:

We are now forced to spend time debugging the environment setup itself, similar to experiences with other suppliers.

---

I dropped you a PM @samsio_innovations to try to discover a little bit more what you mean with the above statement. I have some assumptions, but I don't want to bias the debate. ;) I hope you are willing to reply to my PM.

[samsio_innovations]

Hello Mattias,

Yes, I've replied to you. 

Thanks for your concern. 

[chriskuku]

I'm still sticking with STM32CubeIDE 1.19.0, since the CubeMX IOC editor got banned from the integration into STM32CubeIDE. Has STM refrained from this idea or was it he final word?

If not, what is the way to use STM32CubeIDE in conjunction with the CubeMX IDE-editor (side by side)? Do the ioc files disappear from the project tree view? 

[Andrew Neil]

---

@chriskuku wrote:

Has STM refrained from this idea or was it he final word?

---

I don't see it going back - especially now that we have not only CubeMX but also CubeMX2.

---

@chriskuku wrote:

what is the way to use STM32CubeIDE in conjunction with the CubeMX IDE-editor

---

STM32CubeIDE 2.0.0 New workflow tutorial.

[Pavel A.]

@chriskuku Please feel safe and assured that the 1.x branch is supported and it won't disappear tomorrow. (but maybe, next year :)

[AScha.3]

STM just adheres to Murphy's Law.

1. Any given program, when running, is obsolete.
2. If a program is useful, it will have to be changed.
3. After months of training and you finally understand all of a program's commands, a revised version of the program arrives with an all-new command structure.