Re: failing initialization of KStandardAction/KConfigWatcher on macos

On Freitag, 22. September 2023 18:38:31 CEST Alexander Semke wrote: > Hi, > > we've got a problem reported from a user using labplot on macos. The start > of labplot fails, the application is hanging and the sample of the running > process points to the following call stack: >

failing initialization of KStandardAction/KConfigWatcher on macos

Hi, we've got a problem reported from a user using labplot on macos. The start of labplot fails, the application is hanging and the sample of the running process points to the following call stack: Heaviest stack for the main thread of the target process: 11 start + 1903 (dyld + 25631)

D25877: [KColorschemeManager] Add option to reenable following global theme

asemke added a comment. +1 REPOSITORY R265 KConfigWidgets BRANCH systemthem (branched from master) REVISION DETAIL https://phabricator.kde.org/D25877 To: davidre, #frameworks, ngraham Cc: ahmadsamir, asemke, kossebau, ngraham, kde-frameworks-devel, LeGast00n, GB_2, michaelh, bruns

D25877: [KColorschemeManager] Add option to reenable following global theme

asemke added inline comments. INLINE COMMENTS > davidre wrote in kcolorschememanager.cpp:220 > Should we also do this for the other overloads? Or would that behavior change > be a blocker? ALso an application would want to call > `KColorSchemeManager::createSchemeSelectionMenu(const QString >

D25877: [KColorschemeManager] Add option to reenable following global theme

asemke added inline comments. INLINE COMMENTS > kcolorschememanager.cpp:220 > +{ > +return createSchemeSelectionMenu(QIcon(),QString(), QString(), parent); > +} why not to use reasonable default values here like QIcon::fromTheme(QStringLiteral("preferences-desktop-color") and i18n("Color

D25877: [KColorschemeManager] Add option to reenable following global theme

asemke added inline comments. INLINE COMMENTS > davidre wrote in kcolorschememanager.h:130 > I thought it would be nice to have as a convenience function if an > application has changed the scheme to easily go back to the system color > scheme. I don't know if it should be a slot. I put it

D25877: [KColorschemeManager] Add option to reenable following global theme

asemke added inline comments. INLINE COMMENTS > ngraham wrote in kcolorschememanager.cpp:107 > "Default" is probably fine. > > FWIW the parent menu item is actually mis-named, at least in Kate. It's > called "Color Theme" when it should be "Color Scheme" > > Also this menu should be

D25877: [KColorschemeManager] Add option to reenable following global theme

asemke added inline comments. INLINE COMMENTS > kcolorschememanager.cpp:107 > }); > +m_data.prepend({i18n("System color scheme"), QString(), > QIcon::fromTheme("edit-undo")}); > endResetModel(); Many applications like kdevelop, digikam, labplot, etc. create a menu "Color Scheme"

D23119: Fix dates being on the wrong locale when setting an application language individually

asemke added a comment. In D23119#519676 , @asemke wrote: > The original problem in LabPlot was reported by a windows user. The proposed fix won't fix the problem on windows. I think the only way to get the proper strings on Windows is to get

D23119: Fix dates being on the wrong locale when setting an application language individually

asemke added a comment. In D23119#524720 , @aacid wrote: > In D23119#519676 , @asemke wrote: > > > The original problem in LabPlot was reported by a windows user. The proposed fix won't fix the

D23119: Fix dates being on the wrong locale when setting an application language individually

asemke added a comment. The original problem in LabPlot was reported by a windows user. The proposed fix won't fix the problem on windows. I think the only way to get the proper strings on Windows is to get the current language of the application, to create a QLocale with the proper

D23119: Fix dates being on the wrong locale when setting an application language individually

asemke added inline comments. INLINE COMMENTS > asemke wrote in kxmlgui_unittest.cpp:1089 > This is maybe not Qt but the locale defintion files which are probably distro > specific. I just checked on SLES and on openSuse. > > for ukrainian: > > LC_TIME=uk_UA.UTF-8 locale mon > >

D23119: Fix dates being on the wrong locale when setting an application language individually

asemke added inline comments. INLINE COMMENTS > yurchor wrote in kxmlgui_unittest.cpp:1089 > AFAIK this is broken on Qt level. Cf. calendar widget in KOrganizer > (Ukrainian) > > F7273188: cal.png > > https://bugs.kde.org/show_bug.cgi?id=256952 > >

D23119: Fix dates being on the wrong locale when setting an application language individually

asemke added inline comments. INLINE COMMENTS > ltoscano wrote in kxmlgui_unittest.cpp:1089 > Declensions: > https://en.wiktionary.org/wiki/%D1%8F%D0%BD%D0%B2%D0%B0%D1%80%D1%8C#Declension there is no declension in Russian for the nominative case. The name of the month is январь and not

D23119: Fix dates being on the wrong locale when setting an application language individually

asemke added inline comments. INLINE COMMENTS > kxmlgui_unittest.cpp:1089 > QCOMPARE(QLocale::system().language(), QLocale::Russian); > +QCOMPARE(QLocale::system().monthName(1), QString::fromUtf8("января")); > does this test work? The name of the month is "январь" in russian, not

restore dialog sizes and QTBUG-40584

Hi, after having read the documentation of KWindowConfig::restoreWindowSize(), I understood how to properly restore the dialog sizes. I'm in a process of fixing this now in LabPlot (20 dialogs or so): https://cgit.kde.org/labplot.git/commit/? id=ebfa6b4243dec41b6c656483a57401de4b387793

D15076: Build failures with KSyntaxHighlighting 5.49

asemke added a comment. In D15076#315803 , @cgiboudeaux wrote: > In D15076#315797 , @asemke wrote: > > > > > > > > >

D15076: Build failures with KSyntaxHighlighting 5.49

asemke added a comment. In D15076#315583 , @cgiboudeaux wrote: > In D15076#315506 , @mpyne wrote: > > > I don't know the cause myself but the ECM version works up until 5.38.0 in my own testing. So

D14434: add functions to access keywords

asemke added a comment. In D14434#300211 , @dhaumann wrote: > @asemke Are you sure you reference the correct Task? I cannot find anything about keyword lists in your link. @dhaumann yes, I'm sure this is the correct task. That task is

D14434: add functions to access keywords

asemke accepted this revision. This revision is now accepted and ready to land. REPOSITORY R216 Syntax Highlighting BRANCH keywordlist REVISION DETAIL https://phabricator.kde.org/D14434 To: jpoelen, #framework_syntax_highlighting, dhaumann, asemke Cc: vkrause, cullmann, asemke,

D14434: add functions to access keywords

asemke added a comment. In D14434#299932 , @dhaumann wrote: > In general looks good to me, so +1. I would like to have another +1 from @cullmann, @vkrause or @asemke +1 > What I wonder is whether you really need the keyword lists

Re: how to get the list of keywords in KSyntaxHighlighting

Hi Dominik, > sorry for the delay, I only now saw your mail. > Jonathan meanwhile posted a patch that adds this: > https://phabricator.kde.org/D14434 Yes, I saw it already. Will this make into the 5.49 release of the frameworks? > However, pushing this further, what Kate also needs is a way go

how to get the list of keywords in KSyntaxHighlighting

Hi, I'd like to remove the maintenance of syntax keywords in Cantor (e.g. https:// cgit.kde.org/cantor.git/tree/src/backends/maxima/maximakeywords.cpp) and to switch to KSyntaxHighlighting. Cantor uses its own highlighters and I'd need to get the list of keywords from KSyntaxHighlighter for

D13643: Add LabPlot project file icon

asemke added a comment. Thank for this work. It looks nice to me. However, maybe it's better for people from VDG and Breeze teams to accept this or to raise objections. REPOSITORY R266 Breeze Icons REVISION DETAIL https://phabricator.kde.org/D13643 To: mtrescott, #labplot, #vdg,

Crash on windows when resetting the toolbar items to the default values

Hi, https://bugs.kde.org/show_bug.cgi?id=387610 we've got this bug reported, happens on windows only. Can somebody check this with another KF5-application on windows? Any ideas what is causing this crash? Thanks and Regards, Alexander

proposal to extend and to improve KColorSchemeManager

Hi, I recently switched from using Digikam's code for the handling of color schemes in the application to KColorSchemeManager in LabPlot [1]. It works, but there're couple of things that I miss: * "Default"-entry in the color scheme menu to easily switch to the default desktop color scheme *

Re: save and restore the geometry of KMainWindow

On 01.02.2018 20:52, Albert Astals Cid wrote: El dimarts, 30 de gener de 2018, a les 21:06:02 CET, Alexander Semke va escriure: The state is already saved and restored there. Why not to do the same for the geometry? I think that it's generally frowned upon putting your position on screen

Re: save and restore the geometry of KMainWindow

On 30.01.2018 16:38, Milian Wolff wrote: This works for me: https://github.com/KDAB/hotspot/blob/4d1177d1631902dce1dd82f53553e97a7544b1fa/ src/mainwindow.cpp#L162 Thanks, that helped. I was using restoreGeometry(group.readEntry("geometry").toLatin1()) instead of

Re: save and restore the geometry of KMainWindow

resending this to kde-devel... On 28.01.2018 18:45, Alexander Semke wrote: Hi, KMainWindow takes care of saving/restoring the state of the main window, menus and toolbars. Also, the size of the main window is correctly stored and restored. However, I don't see how to save and restore

save and restore the geometry of KMainWindow

Hi, KMainWindow takes care of saving/restoring the state of the main window, menus and toolbars. Also, the size of the main window is correctly stored and restored. However, I don't see how to save and restore the position of the main window. I checked couple of KDE programs like dolphin,

Re: Default location of the settings file on windows when using KXmlGuiWindow/KMainWindow

On 12.12.2017 13:13, Kåre Särs wrote: On måndag 11 december 2017 kl. 21:55:23 EET Albert Astals Cid wrote: El dijous, 7 de desembre de 2017, a les 22:13:21 CET, Alexander Semke va escriure: Hi all, https://bugs.kde.org/show_bug.cgi?id=387626 we've got this problem reported and I don't see