Hi, I also tried updating my plugin yesterday (SpellChecker Plugin) and it builds fine but I saw it does nothing when I install/test it. This is probably the reason so thanks for the heads up.
my 2c: Although I appreciate that the developers of Qt Creator try to improve the IDE and move forward, it is really sad (and frustrating) for me as a plugin maintainer when stuff like this happens. I don't use Qt Creator any more since it does not support my work environment, not for the last 5 years at least, but I still try to maintain my plugin as far as I can since a lot of people 'depend on it' (big thanks to the community that does most of the maintenance and upgrading the last few releases) After trying to update it I saw it does not behave as expected and started considering sunsetting the plugin since I don't have time to now go and step through code to figure out why it is now silently failing. A breaking change (compiler says no) would have been better in this case, instead of a silent failure like this, at least I would know where to go and fix stuff. For plugin maintainers API stability is essential. I think VS Code should be the new standard. I never have to wait for plugin maintainers to catch up to make new plugin releases after a new version of the tool is released. My guess is the Lua support in QtC is trying to solve this, but to be honest I would rather sunset my QtC plugin and move it to VS Code instead of porting it to Lua for an IDE I unfortunately can't use in my day to day. Anyhow, Glad you got yours working On Thu, 19 Jun 2025 at 08:30, Henry Skoglund <[email protected]> wrote: > Hi, just updated to Qt Creator 17 and it looks good, however when > rebuilding my Qt Creator plugin I got stuck for a bit with this failing: > > auto pe = > qobject_cast<QPlainTextEdit*>(EditorManager::currentEditor()->widget()); > > For almost 15 years that statement served me well and it allowed for > example setting a fatter cursor at Qt Creator start (useful on 4K > screens) but today, it returns a nullptr :-( > > > Instead, the new incantation for Qt Creator 17 (and onwards?) seems to be: > > auto pe = > > qobject_cast<Utils::PlainTextEdit*>(EditorManager::currentEditor()->widget()); > > After that fix, it's smooth sailing (Utils::PlainTextEdit behaves 100% > compatible with QPlainTextEdit). > > But if there was a bit of documentation of this new class in the Utils:: > Namespace I would be even more happy! > Rgrds Henry > > -- > Qt-creator mailing list > [email protected] > https://lists.qt-project.org/listinfo/qt-creator >
-- Qt-creator mailing list [email protected] https://lists.qt-project.org/listinfo/qt-creator
