How to disable beep sound for TextBox while trying to enter more characters than allowed












0















I set MaxLength for my TextBox as 4. When I try to enter 5th character, some Windows system beep sound appears. How to disable it?










share|improve this question




















  • 1





    You can try setting the max to 5 but program it stop responding to keypresses at 4.

    – TGamer
    Jan 7 '18 at 0:56






  • 1





    Can you just tell us if it VB.Net or C#?

    – TGamer
    Jan 7 '18 at 0:56






  • 2





    Possible duplicate of How do I prevent MaxLength beeping or prevent application beeping altogether?

    – Jim Hewitt
    Jan 7 '18 at 1:01











  • @JimHewitt that question is for visuab basic by the way, but is similar

    – user6478676
    Jan 7 '18 at 2:15


















0















I set MaxLength for my TextBox as 4. When I try to enter 5th character, some Windows system beep sound appears. How to disable it?










share|improve this question




















  • 1





    You can try setting the max to 5 but program it stop responding to keypresses at 4.

    – TGamer
    Jan 7 '18 at 0:56






  • 1





    Can you just tell us if it VB.Net or C#?

    – TGamer
    Jan 7 '18 at 0:56






  • 2





    Possible duplicate of How do I prevent MaxLength beeping or prevent application beeping altogether?

    – Jim Hewitt
    Jan 7 '18 at 1:01











  • @JimHewitt that question is for visuab basic by the way, but is similar

    – user6478676
    Jan 7 '18 at 2:15
















0












0








0








I set MaxLength for my TextBox as 4. When I try to enter 5th character, some Windows system beep sound appears. How to disable it?










share|improve this question
















I set MaxLength for my TextBox as 4. When I try to enter 5th character, some Windows system beep sound appears. How to disable it?







c# winforms






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 7 '18 at 2:15

























asked Jan 6 '18 at 22:56







user6478676















  • 1





    You can try setting the max to 5 but program it stop responding to keypresses at 4.

    – TGamer
    Jan 7 '18 at 0:56






  • 1





    Can you just tell us if it VB.Net or C#?

    – TGamer
    Jan 7 '18 at 0:56






  • 2





    Possible duplicate of How do I prevent MaxLength beeping or prevent application beeping altogether?

    – Jim Hewitt
    Jan 7 '18 at 1:01











  • @JimHewitt that question is for visuab basic by the way, but is similar

    – user6478676
    Jan 7 '18 at 2:15
















  • 1





    You can try setting the max to 5 but program it stop responding to keypresses at 4.

    – TGamer
    Jan 7 '18 at 0:56






  • 1





    Can you just tell us if it VB.Net or C#?

    – TGamer
    Jan 7 '18 at 0:56






  • 2





    Possible duplicate of How do I prevent MaxLength beeping or prevent application beeping altogether?

    – Jim Hewitt
    Jan 7 '18 at 1:01











  • @JimHewitt that question is for visuab basic by the way, but is similar

    – user6478676
    Jan 7 '18 at 2:15










1




1





You can try setting the max to 5 but program it stop responding to keypresses at 4.

– TGamer
Jan 7 '18 at 0:56





You can try setting the max to 5 but program it stop responding to keypresses at 4.

– TGamer
Jan 7 '18 at 0:56




1




1





Can you just tell us if it VB.Net or C#?

– TGamer
Jan 7 '18 at 0:56





Can you just tell us if it VB.Net or C#?

– TGamer
Jan 7 '18 at 0:56




2




2





Possible duplicate of How do I prevent MaxLength beeping or prevent application beeping altogether?

– Jim Hewitt
Jan 7 '18 at 1:01





Possible duplicate of How do I prevent MaxLength beeping or prevent application beeping altogether?

– Jim Hewitt
Jan 7 '18 at 1:01













@JimHewitt that question is for visuab basic by the way, but is similar

– user6478676
Jan 7 '18 at 2:15







@JimHewitt that question is for visuab basic by the way, but is similar

– user6478676
Jan 7 '18 at 2:15














2 Answers
2






active

oldest

votes


















0














Based on the discussion with Sievajet, try this other solution:



textBox1.KeyDown += (sender, e) => {
TextBox tBox = sender as TextBox;
if (tBox.Text.Length == tBox.MaxLength)
e.SuppressKeyPress = true;
};


Note:

If you find that both solutions works, please choose Sievajet's answer as the good one, I'm more interested in the result, so maybe write me a comment.






share|improve this answer


























  • Thank you both @Jimi and @Sievajet, I've used only e.SuppressKeyPress = true; and it was fine for me!

    – user6478676
    Jan 8 '18 at 11:47



















1














You can simply fix this with the KeyUp event handler:



textBox1.KeyUp += ( sender , e ) => e.SuppressKeyPress = true;


This will prevent windows to get the max-length signal from the textbox.






share|improve this answer





















  • 1





    Probably e.SuppressKeyPress = true;

    – Jimi
    Jan 6 '18 at 23:32






  • 1





    You're right. e.Handled doesn't take care of pending WM_CHAR messages already built up in the message queue - so setting Handled = true does not prevent a KeyPress from occurring.

    – Sievajet
    Jan 6 '18 at 23:35








  • 1





    It is sent anyway in the KeyDown event. You should change .KeyUp with .KeyDown to suppress it for good.

    – Jimi
    Jan 6 '18 at 23:43






  • 1





    It's not a problem if the keydown event is triggered. This is a one liner in the keyup event and will prevent more characters in the textbox. You'll need to do more checks in the keydown event.

    – Sievajet
    Jan 6 '18 at 23:48








  • 1





    It's missing the check if(TextBox1.Text.Lenght ==4). Just extend the Lambda { }

    – Jimi
    Jan 6 '18 at 23:49













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%2f48132720%2fhow-to-disable-beep-sound-for-textbox-while-trying-to-enter-more-characters-than%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown
























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Based on the discussion with Sievajet, try this other solution:



textBox1.KeyDown += (sender, e) => {
TextBox tBox = sender as TextBox;
if (tBox.Text.Length == tBox.MaxLength)
e.SuppressKeyPress = true;
};


Note:

If you find that both solutions works, please choose Sievajet's answer as the good one, I'm more interested in the result, so maybe write me a comment.






share|improve this answer


























  • Thank you both @Jimi and @Sievajet, I've used only e.SuppressKeyPress = true; and it was fine for me!

    – user6478676
    Jan 8 '18 at 11:47
















0














Based on the discussion with Sievajet, try this other solution:



textBox1.KeyDown += (sender, e) => {
TextBox tBox = sender as TextBox;
if (tBox.Text.Length == tBox.MaxLength)
e.SuppressKeyPress = true;
};


Note:

If you find that both solutions works, please choose Sievajet's answer as the good one, I'm more interested in the result, so maybe write me a comment.






share|improve this answer


























  • Thank you both @Jimi and @Sievajet, I've used only e.SuppressKeyPress = true; and it was fine for me!

    – user6478676
    Jan 8 '18 at 11:47














0












0








0







Based on the discussion with Sievajet, try this other solution:



textBox1.KeyDown += (sender, e) => {
TextBox tBox = sender as TextBox;
if (tBox.Text.Length == tBox.MaxLength)
e.SuppressKeyPress = true;
};


Note:

If you find that both solutions works, please choose Sievajet's answer as the good one, I'm more interested in the result, so maybe write me a comment.






share|improve this answer















Based on the discussion with Sievajet, try this other solution:



textBox1.KeyDown += (sender, e) => {
TextBox tBox = sender as TextBox;
if (tBox.Text.Length == tBox.MaxLength)
e.SuppressKeyPress = true;
};


Note:

If you find that both solutions works, please choose Sievajet's answer as the good one, I'm more interested in the result, so maybe write me a comment.







share|improve this answer














share|improve this answer



share|improve this answer








edited Nov 24 '18 at 3:31

























answered Jan 7 '18 at 2:17









JimiJimi

8,45241934




8,45241934













  • Thank you both @Jimi and @Sievajet, I've used only e.SuppressKeyPress = true; and it was fine for me!

    – user6478676
    Jan 8 '18 at 11:47



















  • Thank you both @Jimi and @Sievajet, I've used only e.SuppressKeyPress = true; and it was fine for me!

    – user6478676
    Jan 8 '18 at 11:47

















Thank you both @Jimi and @Sievajet, I've used only e.SuppressKeyPress = true; and it was fine for me!

– user6478676
Jan 8 '18 at 11:47





Thank you both @Jimi and @Sievajet, I've used only e.SuppressKeyPress = true; and it was fine for me!

– user6478676
Jan 8 '18 at 11:47













1














You can simply fix this with the KeyUp event handler:



textBox1.KeyUp += ( sender , e ) => e.SuppressKeyPress = true;


This will prevent windows to get the max-length signal from the textbox.






share|improve this answer





















  • 1





    Probably e.SuppressKeyPress = true;

    – Jimi
    Jan 6 '18 at 23:32






  • 1





    You're right. e.Handled doesn't take care of pending WM_CHAR messages already built up in the message queue - so setting Handled = true does not prevent a KeyPress from occurring.

    – Sievajet
    Jan 6 '18 at 23:35








  • 1





    It is sent anyway in the KeyDown event. You should change .KeyUp with .KeyDown to suppress it for good.

    – Jimi
    Jan 6 '18 at 23:43






  • 1





    It's not a problem if the keydown event is triggered. This is a one liner in the keyup event and will prevent more characters in the textbox. You'll need to do more checks in the keydown event.

    – Sievajet
    Jan 6 '18 at 23:48








  • 1





    It's missing the check if(TextBox1.Text.Lenght ==4). Just extend the Lambda { }

    – Jimi
    Jan 6 '18 at 23:49


















1














You can simply fix this with the KeyUp event handler:



textBox1.KeyUp += ( sender , e ) => e.SuppressKeyPress = true;


This will prevent windows to get the max-length signal from the textbox.






share|improve this answer





















  • 1





    Probably e.SuppressKeyPress = true;

    – Jimi
    Jan 6 '18 at 23:32






  • 1





    You're right. e.Handled doesn't take care of pending WM_CHAR messages already built up in the message queue - so setting Handled = true does not prevent a KeyPress from occurring.

    – Sievajet
    Jan 6 '18 at 23:35








  • 1





    It is sent anyway in the KeyDown event. You should change .KeyUp with .KeyDown to suppress it for good.

    – Jimi
    Jan 6 '18 at 23:43






  • 1





    It's not a problem if the keydown event is triggered. This is a one liner in the keyup event and will prevent more characters in the textbox. You'll need to do more checks in the keydown event.

    – Sievajet
    Jan 6 '18 at 23:48








  • 1





    It's missing the check if(TextBox1.Text.Lenght ==4). Just extend the Lambda { }

    – Jimi
    Jan 6 '18 at 23:49
















1












1








1







You can simply fix this with the KeyUp event handler:



textBox1.KeyUp += ( sender , e ) => e.SuppressKeyPress = true;


This will prevent windows to get the max-length signal from the textbox.






share|improve this answer















You can simply fix this with the KeyUp event handler:



textBox1.KeyUp += ( sender , e ) => e.SuppressKeyPress = true;


This will prevent windows to get the max-length signal from the textbox.







share|improve this answer














share|improve this answer



share|improve this answer








edited Jan 6 '18 at 23:44

























answered Jan 6 '18 at 23:29









SievajetSievajet

2,98321322




2,98321322








  • 1





    Probably e.SuppressKeyPress = true;

    – Jimi
    Jan 6 '18 at 23:32






  • 1





    You're right. e.Handled doesn't take care of pending WM_CHAR messages already built up in the message queue - so setting Handled = true does not prevent a KeyPress from occurring.

    – Sievajet
    Jan 6 '18 at 23:35








  • 1





    It is sent anyway in the KeyDown event. You should change .KeyUp with .KeyDown to suppress it for good.

    – Jimi
    Jan 6 '18 at 23:43






  • 1





    It's not a problem if the keydown event is triggered. This is a one liner in the keyup event and will prevent more characters in the textbox. You'll need to do more checks in the keydown event.

    – Sievajet
    Jan 6 '18 at 23:48








  • 1





    It's missing the check if(TextBox1.Text.Lenght ==4). Just extend the Lambda { }

    – Jimi
    Jan 6 '18 at 23:49
















  • 1





    Probably e.SuppressKeyPress = true;

    – Jimi
    Jan 6 '18 at 23:32






  • 1





    You're right. e.Handled doesn't take care of pending WM_CHAR messages already built up in the message queue - so setting Handled = true does not prevent a KeyPress from occurring.

    – Sievajet
    Jan 6 '18 at 23:35








  • 1





    It is sent anyway in the KeyDown event. You should change .KeyUp with .KeyDown to suppress it for good.

    – Jimi
    Jan 6 '18 at 23:43






  • 1





    It's not a problem if the keydown event is triggered. This is a one liner in the keyup event and will prevent more characters in the textbox. You'll need to do more checks in the keydown event.

    – Sievajet
    Jan 6 '18 at 23:48








  • 1





    It's missing the check if(TextBox1.Text.Lenght ==4). Just extend the Lambda { }

    – Jimi
    Jan 6 '18 at 23:49










1




1





Probably e.SuppressKeyPress = true;

– Jimi
Jan 6 '18 at 23:32





Probably e.SuppressKeyPress = true;

– Jimi
Jan 6 '18 at 23:32




1




1





You're right. e.Handled doesn't take care of pending WM_CHAR messages already built up in the message queue - so setting Handled = true does not prevent a KeyPress from occurring.

– Sievajet
Jan 6 '18 at 23:35







You're right. e.Handled doesn't take care of pending WM_CHAR messages already built up in the message queue - so setting Handled = true does not prevent a KeyPress from occurring.

– Sievajet
Jan 6 '18 at 23:35






1




1





It is sent anyway in the KeyDown event. You should change .KeyUp with .KeyDown to suppress it for good.

– Jimi
Jan 6 '18 at 23:43





It is sent anyway in the KeyDown event. You should change .KeyUp with .KeyDown to suppress it for good.

– Jimi
Jan 6 '18 at 23:43




1




1





It's not a problem if the keydown event is triggered. This is a one liner in the keyup event and will prevent more characters in the textbox. You'll need to do more checks in the keydown event.

– Sievajet
Jan 6 '18 at 23:48







It's not a problem if the keydown event is triggered. This is a one liner in the keyup event and will prevent more characters in the textbox. You'll need to do more checks in the keydown event.

– Sievajet
Jan 6 '18 at 23:48






1




1





It's missing the check if(TextBox1.Text.Lenght ==4). Just extend the Lambda { }

– Jimi
Jan 6 '18 at 23:49







It's missing the check if(TextBox1.Text.Lenght ==4). Just extend the Lambda { }

– Jimi
Jan 6 '18 at 23:49




















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%2f48132720%2fhow-to-disable-beep-sound-for-textbox-while-trying-to-enter-more-characters-than%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







Popular posts from this blog

404 Error Contact Form 7 ajax form submitting

How to know if a Active Directory user can login interactively

TypeError: fit_transform() missing 1 required positional argument: 'X'