The Following 4 Users Say Thank You to pichlo For This Useful Post: | ||
![]() |
2014-05-11
, 14:38
|
|
Posts: 1,986 |
Thanked: 7,698 times |
Joined on Dec 2010
@ Dayton, Ohio
|
#12
|
Another problem is that the Qt version crashes when trying to display too many characters (such as all of them). This is caused by every character being a separate button and it looks like Qt does not like forms with thousands of buttons in them.
The Following 3 Users Say Thank You to Copernicus For This Useful Post: | ||
![]() |
2014-05-11
, 16:13
|
Posts: 23 |
Thanked: 10 times |
Joined on May 2014
@ Germany
|
#13
|
![]() |
2014-05-13
, 14:25
|
|
Posts: 6,450 |
Thanked: 20,983 times |
Joined on Sep 2012
@ UK
|
#14
|
Well, I'd have to agree with Qt on this one, a single form with thousands of individual buttons does seem a bit cumbersome.
I think it might be better to use a QListWidget (or QListView) to display the characters; if you set "flow" to "QListView::LeftToRight", and "isWrapping" to true, Qt should be able to get the characters laid out in a pretty good manner.
The Following User Says Thank You to pichlo For This Useful Post: | ||
![]() |
2014-05-13
, 17:56
|
|
Posts: 1,986 |
Thanked: 7,698 times |
Joined on Dec 2010
@ Dayton, Ohio
|
#15
|
I have been experimenting with that and must say it can be made to work pretty well, but at the cost of losing the buttons. I see little point switching to Qt to get the exact same look as I do with the GTK version, so I may as well stick with GTK. The GTK binary is also about half the size, works faster and has fewer dependencies.
QListView::item{ background:qlineargradient( spread:pad, x1:0, y1:0, x2:0, y2:1, stop:0 rgba(80, 80, 80, 255), stop:0.8 rgba(80, 80, 80, 255), stop:1 rgba(48, 48, 48, 255)); border-width: 1px; border-style: solid; border-radius: 12px; border-color:rgba(80,80,80,255); } QListView::item:selected{ background:qlineargradient( spread:pad, x1:0, y1:0, x2:0, y2:1, stop:0 rgba(128, 128, 128, 255), stop:0.8 rgba(128, 128, 128, 255), stop:1 rgba(48,48,48,255)); }
The Following 3 Users Say Thank You to Copernicus For This Useful Post: | ||
![]() |
2014-05-13
, 22:30
|
|
Posts: 6,450 |
Thanked: 20,983 times |
Joined on Sep 2012
@ UK
|
#16
|
Well, I suspect that part of the reason why the GTK version is able to handle so many characters is that it isn't using full-fledged buttons.
The Following 5 Users Say Thank You to pichlo For This Useful Post: | ||
![]() |
2014-05-17
, 11:28
|
|
Posts: 6,450 |
Thanked: 20,983 times |
Joined on Sep 2012
@ UK
|
#17
|
![]() |
2014-05-17
, 13:14
|
|
Posts: 1,986 |
Thanked: 7,698 times |
Joined on Dec 2010
@ Dayton, Ohio
|
#18
|
For some reason FAM does not show the changelog. It says "not available". Have any developers here experienced something of that kind and know what may have caused it?
The Following User Says Thank You to Copernicus For This Useful Post: | ||
![]() |
2014-05-17
, 14:25
|
Posts: 2,292 |
Thanked: 4,135 times |
Joined on Apr 2010
@ UK
|
#19
|
Version 1.0.1 has arrived in extras-devel.
For some reason FAM does not show the changelog. It says "not available". Have any developers here experienced something of that kind and know what may have caused it? The changelog file is provided with the sources of course.
The Following 3 Users Say Thank You to sixwheeledbeast For This Useful Post: | ||
![]() |
2014-05-17
, 15:42
|
|
Posts: 6,450 |
Thanked: 20,983 times |
Joined on Sep 2012
@ UK
|
#20
|
The Following 3 Users Say Thank You to pichlo For This Useful Post: | ||
In the meantime, you can use the cursor keys to navigate through the character table. The highlighted character details on the right will still get updated but without entering the characters into the edit box. Any accidentally entered character can also be deleted from the box by simply editing the box.
One workaround would be to never enter characters on touch, only highlight them. Then having a button in the right panel for actually entering the character. I had considered it but thought it was a bit clunky. I would welcome people's opinion on the matter.
The part below describes a potential future update, please do not confuse it with the current release.
I have an experimental Qt version in the works. It works a bit better: to start with, scrolling is not registered as a button press. The cells in the character table look like real buttons which I find more aesthetically pleasing. They can also be made smaller so I can get a row of 8 characters instead of 5 (the map as it is now is painted by libgucharmap7 itself and I have no control over the parameters). Only the valid characters can be put on the map rather than all characters with blanks for non-printable ones as it is now. And, last but not least, I have it working in portrait as well as landscape.
Here is a little taster:
Unfortunately there are a few little problems with it. I cannot choose the character set. That is an API call to libgucharmap7 that tells it what to draw. I have not yet found a way to squeeze the list of characters out of it, without letting it draw anything. And, despite trying hard, I have not found any description of the API anywhere, so I could only go with what I could glean from the headers and what scv-reader used.
Another problem is that the Qt version crashes when trying to display too many characters (such as all of them). This is caused by every character being a separate button and it looks like Qt does not like forms with thousands of buttons in them.
So I had to go with the GTK version for the time being.
Русский военный корабль, иди нахуй!