We're past 5.14 and into 5.15 territory now. Does this deserve another look?

• Clear the extruder list before updating
• Clear fan selector before updating

• Rebase

• Add basic range check to prevent overflow of uints

• Clean warning for job progress

Only fixed Modulo Shift.

Also, I made some error to Modulo Shift modes. So, fixed in that differential link.

• patrick Suggestions

• Remove un needed parentheses

What's the status of this?

How is this looking now that D15426 has gone in?

For what it's worth, I notice that ElementaryOS is already doing this:

+1; "Tap to Click" is by far the more commonly used and understood string.

Update "Mouse Click Emulation" to "Tap to Click"

(also, thank you for doing all this work!)

So this doesn't completely fix https://bugs.kde.org/show_bug.cgi?id=375765? More is needed?

In D15532#330269, @rjvbb wrote:

I have no (big) problems with a fallthrough attribute, but if it's going to be obligatory I'd want the complementary attribute (the break) to be obligatory too...

Remove parent directory check entirely; it's not necessary

Oh wow, you're right. Let me fix balooctl to support that, then.

In D15692#330285, @woltherav wrote:

In D15692#330282, @pino wrote:

Not sure I understand, what is the exact workflow that involves writing a .pot file, and reading .po files? Is it because peruse so far is not translatable?
If so, then it'd be much better to extract the messages, and make sure to use ki18n to translate the strings at runtime, just like all the other applications.

Ah, no, what this is for is something else. You see, Peruse Creator makes cbz(comic book) files, and also generates metadata files for cbz, this is done in the ACBF format. The ACBF format supports metadata for text within the comic and holding translations for said text. I figured that it'd be helpful to be able to take these translatable entries, and generate POT files for them (as well as import of translation po files). That way people who'd want to translate a comic can use their favourite pot/po compatible translation tools.

In D15589#330276, @abetts wrote:

If that's the case, do we have just a trash icon, without the folder?

In D15117#330209, @davidedmundson wrote:

To clarify this. Qt currently (should!) have tooltips as popups.

In D15692#330282, @pino wrote:

Not sure I understand, what is the exact workflow that involves writing a .pot file, and reading .po files? Is it because peruse so far is not translatable?
If so, then it'd be much better to extract the messages, and make sure to use ki18n to translate the strings at runtime, just like all the other applications.

In D15644#330281, @lsartorelli wrote:

Hi Nathaniel, thanks for all the support.
I can understand and agree with your concerns.
Not sure but maybe an option could be to add the hide menu bar entry in the setting menu via kxmlguiwindow

Ah but won't that menu become invisible once the menubar is disabled?

Not sure I understand, what is the exact workflow that involves writing a .pot file, and reading .po files? Is it because peruse so far is not translatable?
If so, then it'd be much better to extract the messages, and make sure to use ki18n to translate the strings at runtime, just like all the other applications.

Hi Nathaniel, thanks for all the support.
I can understand and agree with your concerns.
Not sure but maybe an option could be to add the hide menu bar entry in the setting menu via kxmlguiwindow and another entry to unhide it maybe can be putted in the context menu on the window title bar.
Just an idea, that requires wider discussions and knowledges.

I'm not sure... You can try building a Kirigami application that uses Kirigami as a qmake submodule, like Kaidan.

How can I reproduce broken build? Any test plan?