Hook QLineEdit showing text

Multi tool use
Multi tool use












0















Here is my problem.
I type some text into myLineEdit, for example "123456789 987654321", and I want to hide some substring in LineEdit, say "23" when displaying is hidden by another symbol "x". That's what i want to see "1x456789 987654321", but myLineEdit->text() must still return the correct string without replacements ("123456789 987654321").
So what what will help me to do this?










share|improve this question


















  • 3





    Create an inheritance class and implement there that kind of a behaviour

    – Alexander Chernin
    Dec 29 '18 at 21:44
















0















Here is my problem.
I type some text into myLineEdit, for example "123456789 987654321", and I want to hide some substring in LineEdit, say "23" when displaying is hidden by another symbol "x". That's what i want to see "1x456789 987654321", but myLineEdit->text() must still return the correct string without replacements ("123456789 987654321").
So what what will help me to do this?










share|improve this question


















  • 3





    Create an inheritance class and implement there that kind of a behaviour

    – Alexander Chernin
    Dec 29 '18 at 21:44














0












0








0








Here is my problem.
I type some text into myLineEdit, for example "123456789 987654321", and I want to hide some substring in LineEdit, say "23" when displaying is hidden by another symbol "x". That's what i want to see "1x456789 987654321", but myLineEdit->text() must still return the correct string without replacements ("123456789 987654321").
So what what will help me to do this?










share|improve this question














Here is my problem.
I type some text into myLineEdit, for example "123456789 987654321", and I want to hide some substring in LineEdit, say "23" when displaying is hidden by another symbol "x". That's what i want to see "1x456789 987654321", but myLineEdit->text() must still return the correct string without replacements ("123456789 987654321").
So what what will help me to do this?







c++ qt






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 29 '18 at 21:15









Дмитрий СуворовДмитрий Суворов

83




83








  • 3





    Create an inheritance class and implement there that kind of a behaviour

    – Alexander Chernin
    Dec 29 '18 at 21:44














  • 3





    Create an inheritance class and implement there that kind of a behaviour

    – Alexander Chernin
    Dec 29 '18 at 21:44








3




3





Create an inheritance class and implement there that kind of a behaviour

– Alexander Chernin
Dec 29 '18 at 21:44





Create an inheritance class and implement there that kind of a behaviour

– Alexander Chernin
Dec 29 '18 at 21:44












1 Answer
1






active

oldest

votes


















0














Hope this would be helpful. Instead of calling setText(QString) and text(), call setLineText(QString) and getText().



#include <qlineedit.h>
class LineEdit :public QLineEdit
{
Q_OBJECT
LineEdit();
~LineEdit();
QString hide_txt="23";
void setLineText(QString txt) {
txt.replace(hide_txt, "x");
setText(txt);}
QString getText() {
QString txt = text();
txt.replace("x", hide_txt);
return txt;
}

};





share|improve this answer
























  • Does it work if the user enters the text using the GUI non-programmatically?

    – eyllanesc
    Dec 29 '18 at 22:09











  • if the line edit is editable we have to use textChanged(const QString &text) signal and connect it to setLineText(QString)

    – Veera
    Dec 29 '18 at 22:14











  • and do not you think it generated an infinite loop? since according to your logic textChanged would call setLineText, and setLineText calls setText internally to call textChanged, textChanged would call setLineText and returned we will return to the beginning.

    – eyllanesc
    Dec 29 '18 at 22:17











  • you are correct. we have to use textEdited(const QString &text) to avoid infinite loop instead of textChanged()

    – Veera
    Dec 29 '18 at 22:20













Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53973391%2fhook-qlineedit-showing-text%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Hope this would be helpful. Instead of calling setText(QString) and text(), call setLineText(QString) and getText().



#include <qlineedit.h>
class LineEdit :public QLineEdit
{
Q_OBJECT
LineEdit();
~LineEdit();
QString hide_txt="23";
void setLineText(QString txt) {
txt.replace(hide_txt, "x");
setText(txt);}
QString getText() {
QString txt = text();
txt.replace("x", hide_txt);
return txt;
}

};





share|improve this answer
























  • Does it work if the user enters the text using the GUI non-programmatically?

    – eyllanesc
    Dec 29 '18 at 22:09











  • if the line edit is editable we have to use textChanged(const QString &text) signal and connect it to setLineText(QString)

    – Veera
    Dec 29 '18 at 22:14











  • and do not you think it generated an infinite loop? since according to your logic textChanged would call setLineText, and setLineText calls setText internally to call textChanged, textChanged would call setLineText and returned we will return to the beginning.

    – eyllanesc
    Dec 29 '18 at 22:17











  • you are correct. we have to use textEdited(const QString &text) to avoid infinite loop instead of textChanged()

    – Veera
    Dec 29 '18 at 22:20


















0














Hope this would be helpful. Instead of calling setText(QString) and text(), call setLineText(QString) and getText().



#include <qlineedit.h>
class LineEdit :public QLineEdit
{
Q_OBJECT
LineEdit();
~LineEdit();
QString hide_txt="23";
void setLineText(QString txt) {
txt.replace(hide_txt, "x");
setText(txt);}
QString getText() {
QString txt = text();
txt.replace("x", hide_txt);
return txt;
}

};





share|improve this answer
























  • Does it work if the user enters the text using the GUI non-programmatically?

    – eyllanesc
    Dec 29 '18 at 22:09











  • if the line edit is editable we have to use textChanged(const QString &text) signal and connect it to setLineText(QString)

    – Veera
    Dec 29 '18 at 22:14











  • and do not you think it generated an infinite loop? since according to your logic textChanged would call setLineText, and setLineText calls setText internally to call textChanged, textChanged would call setLineText and returned we will return to the beginning.

    – eyllanesc
    Dec 29 '18 at 22:17











  • you are correct. we have to use textEdited(const QString &text) to avoid infinite loop instead of textChanged()

    – Veera
    Dec 29 '18 at 22:20
















0












0








0







Hope this would be helpful. Instead of calling setText(QString) and text(), call setLineText(QString) and getText().



#include <qlineedit.h>
class LineEdit :public QLineEdit
{
Q_OBJECT
LineEdit();
~LineEdit();
QString hide_txt="23";
void setLineText(QString txt) {
txt.replace(hide_txt, "x");
setText(txt);}
QString getText() {
QString txt = text();
txt.replace("x", hide_txt);
return txt;
}

};





share|improve this answer













Hope this would be helpful. Instead of calling setText(QString) and text(), call setLineText(QString) and getText().



#include <qlineedit.h>
class LineEdit :public QLineEdit
{
Q_OBJECT
LineEdit();
~LineEdit();
QString hide_txt="23";
void setLineText(QString txt) {
txt.replace(hide_txt, "x");
setText(txt);}
QString getText() {
QString txt = text();
txt.replace("x", hide_txt);
return txt;
}

};






share|improve this answer












share|improve this answer



share|improve this answer










answered Dec 29 '18 at 22:06









VeeraVeera

749




749













  • Does it work if the user enters the text using the GUI non-programmatically?

    – eyllanesc
    Dec 29 '18 at 22:09











  • if the line edit is editable we have to use textChanged(const QString &text) signal and connect it to setLineText(QString)

    – Veera
    Dec 29 '18 at 22:14











  • and do not you think it generated an infinite loop? since according to your logic textChanged would call setLineText, and setLineText calls setText internally to call textChanged, textChanged would call setLineText and returned we will return to the beginning.

    – eyllanesc
    Dec 29 '18 at 22:17











  • you are correct. we have to use textEdited(const QString &text) to avoid infinite loop instead of textChanged()

    – Veera
    Dec 29 '18 at 22:20





















  • Does it work if the user enters the text using the GUI non-programmatically?

    – eyllanesc
    Dec 29 '18 at 22:09











  • if the line edit is editable we have to use textChanged(const QString &text) signal and connect it to setLineText(QString)

    – Veera
    Dec 29 '18 at 22:14











  • and do not you think it generated an infinite loop? since according to your logic textChanged would call setLineText, and setLineText calls setText internally to call textChanged, textChanged would call setLineText and returned we will return to the beginning.

    – eyllanesc
    Dec 29 '18 at 22:17











  • you are correct. we have to use textEdited(const QString &text) to avoid infinite loop instead of textChanged()

    – Veera
    Dec 29 '18 at 22:20



















Does it work if the user enters the text using the GUI non-programmatically?

– eyllanesc
Dec 29 '18 at 22:09





Does it work if the user enters the text using the GUI non-programmatically?

– eyllanesc
Dec 29 '18 at 22:09













if the line edit is editable we have to use textChanged(const QString &text) signal and connect it to setLineText(QString)

– Veera
Dec 29 '18 at 22:14





if the line edit is editable we have to use textChanged(const QString &text) signal and connect it to setLineText(QString)

– Veera
Dec 29 '18 at 22:14













and do not you think it generated an infinite loop? since according to your logic textChanged would call setLineText, and setLineText calls setText internally to call textChanged, textChanged would call setLineText and returned we will return to the beginning.

– eyllanesc
Dec 29 '18 at 22:17





and do not you think it generated an infinite loop? since according to your logic textChanged would call setLineText, and setLineText calls setText internally to call textChanged, textChanged would call setLineText and returned we will return to the beginning.

– eyllanesc
Dec 29 '18 at 22:17













you are correct. we have to use textEdited(const QString &text) to avoid infinite loop instead of textChanged()

– Veera
Dec 29 '18 at 22:20







you are correct. we have to use textEdited(const QString &text) to avoid infinite loop instead of textChanged()

– Veera
Dec 29 '18 at 22:20




















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53973391%2fhook-qlineedit-showing-text%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







alGZi04nHjGe O lKocuiVgS JNL58B83os1n wYj
z7JQPMcvx1,wNjNrJ5Ks9RV9OTNl,wUajNeqK8H3H9PzLZAXlR lTJ2njCl6oN5BLK 2geDRGC

Popular posts from this blog

Monofisismo

Angular Downloading a file using contenturl with Basic Authentication

Olmecas