@candy76041820 said in Why cling onto RegEx?:

1a. Well it's just a makeshift & demonstrative snippet to convey my idea of usting something instead of regex, so don't be so picky.

Your point was to demonstrate that a simpler solution was available. However, if you can't demonstrate that the simpler solution does everything required then it isn't a solution and you haven't demonstrated anything. It's hardly being "picky" to point this out!

@raven-worx i cannot specify Layout.alignment in string creating Text because i get error that this property doesn't exist

I found out that I can reproduce this behavior by setting QT_DISTANCEFIELD_DEFAULT_BASEFONTSIZE, QT_DISTANCEFIELD_DEFAULT_SCALE and QT_DISTANCEFIELD_DEFAULT_RADIUS variables. With these, the problem occurs even on Windows.

Not sure whether it's the same problem or not, but if QT_DISTANCEFIELD_DEFAULT_RADIUS is NOT DIVISIBLE by QT_DISTANCEFIELD_DEFAULT_SCALE, the problem occurs 100% of time (some letters will disappear).

Example:
export QT_DISTANCEFIELD_DEFAULT_BASEFONTSIZE=128
export QT_DISTANCEFIELD_DEFAULT_SCALE=12
export QT_DISTANCEFIELD_DEFAULT_RADIUS=96 // If I set this to 95 or 97 or anything not divisible by 12, it will break.

Can someone explain me what these distancefield environment variables do and whether this is an intended behavior?

@J-Hilk thank you

No need to calculate the position, use linkActivated signal handler https://doc.qt.io/qt-5/qml-qtquick-text.html#linkActivated-signal

Is it possible to to extend QLabel and implement my own paintEvent() that draws the text and draws the svg image?

It seems to work, but would problaby take alot of effort to get it right (i.e. to get the image in the right location everytime).

void MypLabel::paintEvent(QPaintEvent* event) { QPainter painter(this); const auto pos = QPoint(0, 16); painter.drawText(pos, this->text()); const auto posPixMap = QPoint(30, 0); auto size = QSize(16, 16); auto pixMap = QIcon(":/Resources/smiley.svg").pixmap(size); painter.drawPixmap(posPixMap, pixMap); }

@mrjj Thank you for your answer. So I tested to remove the text rectangle passed to the drawContents() function, and indeed the global clipping was applied instead.

@diredko
you can take a look at the Scalability section of the documentation

The calculating scaling ratio section has an example that used to help me a lot when I first was confronted with this issue.

I resolve it.

I setted font of text as property of QML Text component.
(Like font.family : parent.fontfamily)

and on Qt 5.7's QML, there are no enough options to control font properties.

so, I moved to C++ side and set a whole application font.

QFont font = someClass.getLangFont();
//set property of font instance here
// such as hinting policy, style etc.
QApplication::setFont(font);

now it looks very cleary...

thank you..

I've got the same issue with Qt3DExtras::QText2DEntity. But I found the workaround.
Look like there is a bug? in implementation of Qt3DExtras::QText2DEntity that prevents internal initialization (QText2DEntityPrivate::setScene is never called). This happens when scene is already visible and Qt3DExtras::QText2DEntity is created with parent entity passed to constructor. The workaround I used to make it work is to pass nullptr (which is default) as parent in constructor and call ->setParent(parentEntity) in separate call.

m_text2dLabel = new Qt3DExtras::QText2DEntity(); m_text2dLabel->setParent(parentNode);

@aha_1980 Thanks for the answer . I will try your sugestions and see how it goes. I've done all this text to ASCII in console codeblocks C++ but it seems that i need a gui to it. I am not as good in Class'es and things like that. I will try it anyways. An example could be more than good for one letter . i could do the rest alone :P . Have a good night

Looks strange. There is one example called fontDatabase in Qt examples. Can you compile in msvc and check this font is available ?

@romsharkov said in Incorrect Font Metrics:

@raven-worx Didn't know about those methods, just tested it, for the lower case letter "g":
QFontMetricsF::leftBearing() returns: -4.17188
QFontMetricsF::rightBearing() returns: 0.6875
But even if I add the (negated) leftBearing to the total text width it still doesn't cover the tail entirely, so what's wrong here?

are you sure?!
Those values seem to be correct / make sense according to your posted screens.

Make sure that you add the absolute value (qAbs() for example). Also keep in mind that those values are only correct for the given font-size and that you can't add negative values to a image width.
I guess you are just doing incorrect calculations. Can you show the code of the calculation?

Hi,

As silly as it may sound but wouldn't removing << std::endl from the checking line be enough ?

Ok, thanks a lot! Marked as solved!

QComboBox {background-color:rgb(190,190,190);color:black;padding-left: 10px;padding-right: 30px;border-style: solid;border-width: 0px;}

"padding-left: 10px;"

the padding will shift the combo-box displayed content form the left edge

QComboBox::drop-down {subcontrol-origin: padding; subcontrol-position: top right;width: 40px;border: 0px ;}

"subcontrol-position: top right;"

and the above will position wot text to the right.

Hopefully this helps.

@Rohith
instead of converting the unicode string to the escaped characters send it directly in binary form. When you have a QString already you can call QString::toUtf8() and send the returned QByteArray directly. On the client its enough to do QString::fromUtf8( receivedUtf8ByteArray.constData() )

It depends how you implemented the transfer.
But theoretically it should be enough to replace your unicode escaping code on the server with this approach.