[Feature suggestion] Add strikeout button in comment function about harbour-storeman HOT 4 CLOSED

A better idea for reducing the width of the "< >" button (than reducing its font size or margins) is to use a smaller space between the two brackets, e.g. the Unicode code point U+200A "Hair space" (i.e. < >), U+2009 "Thin space" (i.e. < >) or U+2006 "Six-per-EM space". Actually the U+200A "Hair space" looks best and most reasonable to me.

from harbour-storeman.

Oh, I missed to reason why a strikeout button is needed, IMO:
Strikeout is quite useful when correcting comments which already have follow-up comments, in order not to disrupt the reading flow for others (i.e. not to render the follow-up comments idiotic).

from harbour-storeman.

Hi,
I also think that all buttons should have the same width but I don't know how to show for example the pre tag. About the code tag - there is no space between brackets at all.

https://github.com/mentaljam/harbour-storeman/blob/dd762bffd51d590419a1abd1ff5aecfe2b4834cb/harbour-storeman/qml/components/CommentField.qml#L157

Also note that the buttons widget is flickable and could be swiped to the left/right. So some buttons could be "hidden" and a hint to swipe could be showed to the user on the first use.

from harbour-storeman.

Thanks for your prompt reply and the pointer to the code. Well, while reading your reply, I thought "Oh", and "Oh, again", as I did neither expect setting the button width to a fixed size and having its content "fit to size" being impossible or being unable to set the font size.
Well, before HTML5 the font tag supported a size attribute, e.g. <font face="monospace" size=2>foo</font>, maybe it is worth a try.
Otherwise the only option I can currently see to shrink the oversized "< >" and "pre" button content is to use a different font than monospace. On first thought, the regular font with "< >" separated by aforementioned hair space (plus maybe set in bold) and "pre" set in bold might fit well.

But as the whole button line is flickable, a "strikeout" button (preferably inserted between the "underline" and "quote" buttons) seems to be feasible (at least under GUI aspects), right?

from harbour-storeman.