Review Request 129324: VCSCommitDiffPatchSource point changes : set width to 72 characters and use deleteLater()

Aleix Pol Gonzalez aleixpol at kde.org
Tue Nov 8 23:23:16 UTC 2016



> On Nov. 8, 2016, 8:48 p.m., Aleix Pol Gonzalez wrote:
> > plugins/git/gitmessagehighlighter.cpp, line 41
> > <https://git.reviewboard.kde.org/r/129324/diff/2/?file=484065#file484065line41>
> >
> >     -1
> 
> René J.V. Bertin wrote:
>     Well, the goal is to draw attention... :) I considered overstrike which would be the most logical choice if it didn't affect readability a bit too much (but I didn't try it yet).
>     
>     What other options are there that cannot be mistaken for information from the spellchecker and that also don't cannot make you wonder if you just typed a space or an underscore?

I tested it, my brain was saying it was an underline on the line above.
Maybe strike would work, or changing the font color.


- Aleix


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/129324/#review100734
-----------------------------------------------------------


On Nov. 4, 2016, 6:07 p.m., René J.V. Bertin wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/129324/
> -----------------------------------------------------------
> 
> (Updated Nov. 4, 2016, 6:07 p.m.)
> 
> 
> Review request for KDE Software on Mac OS X and KDevelop.
> 
> 
> Repository: kdevplatform
> 
> 
> Description
> -------
> 
> This patch proposes 2 point changes to `VCSCommitDiffPatchSource`. They're unrelated but both so small and limited to a single file that I hope you won't mind I put them in a single RR.
> 
> In order of appearance:
> 
> 1- KDE insists on a 72 character limit for commit messages, and that is probably a very reasonable standard. In the current implementation there is no easy way to judge how far from that threshold we are. The easiest way to do this is by setting the commit message editor to a width of 72 characters (which for some reason requires taking the width of a string of 74 characters). I think there is room enough for this, but a more complete implementation would probably introduce a resize handle between the 2 main widgets. I haven't yet tried to look into that.
> 
> 2- The commit message has been a very likely source of the crashes I've seen in the past (on Mac) when closing patch reviews, and which have been addressed by using `QObject::deleteLater()` for select widgets. That change was somehow never submitted for the commit message editor.
> 
> 
> Diffs
> -----
> 
>   plugins/git/gitmessagehighlighter.cpp da7660d 
>   vcs/widgets/vcsdiffpatchsources.cpp 42cf1d8 
> 
> Diff: https://git.reviewboard.kde.org/r/129324/diff/
> 
> 
> Testing
> -------
> 
> On OS X with 2 different fixed font typefaces (sizes). The deleteLater() change has been in use since about 4.7.1 .
> 
> 
> File Attachments
> ----------------
> 
> preview: 72-char wide commit message editor
>   https://git.reviewboard.kde.org/media/uploaded/files/2016/11/03/2ffdd73a-db19-4bf2-9545-7a850a4b7fd1__Screen_Shot_2016-11-03_at_18.24.54.png
> 
> 
> Thanks,
> 
> René J.V. Bertin
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-mac/attachments/20161108/dbea27b8/attachment.html>


More information about the kde-mac mailing list