Skip to main content

WPF Multiline TextBox

ඔන්න අපි හදන්නේ අදත් පුංචි Tip එකක් දෙන්න. මේ ප්‍රශ්නේ මට අවේ මම පොඩි WPF Window එකක් design කර කර ඉන්නකොට.

අපි කොහොමද WPF වලදී Multiline TextBox එකක් හදාගන්නේ කියන එක තමා ඉතින් ප්‍රශ්නේ.

මුලින්ම මම කලේ ඉතින් නිකම්ම TextBox control එකක් දාගෙන එකේ තියෙන Properties එක එක බැලුව මේ වැඩේ කරගන්න විදියක් තියෙනවද කියල. මොකද Windows Forms වල නම් තියෙනවා නේ Property එකක් කෙලින්ම Multiline කියලම. ඒක true කරපු ගමන් බඩු වැඩ. ඒත් කරුමෙට මේකේ එහෙම Property එකක් තිබ්බෙත් නෑ.
පස්සේ මම ඉතින් කවදත් අපේ උදව්වට ඉන්න Google ගෙන් අහල බැලුව. මෙන්න උත්තරේ. ඇත්තටම අපිට WPF වලදී මේක ගොඩ දාගන්න Properties 3 ක් ඕනේ වෙනවා.
පහල තියෙන්නේ ඒකට අදාල xaml markup එක.

<TextBox Name="TextDescription" Height="60" Width="250" Margin="10,0,0,0" VerticalScrollBarVisibility="Visible" AcceptsReturn="True" TextWrapping="Wrap"/>

ඔන්න අපට වැදගත් වෙන එව්වා underline කරලම තියෙනවා.


VerticalScrollBarVisibility කියල කියන්නේ අපිට මේකේ scroll bar එකක් පෙන්නන්න ඕනෙද කියන එක. මේක set කරන එක අත්‍යවශ්‍යම නෑ, ඒත් ඉතින් තිබුනොත් හොඳයි.

AcceptsReturn මේකෙන් කියවෙන්නේ අපි Enter key එක press කලොත් ඒක Enter එකක් විදියට බාර ගන්න කියන්න එක, එතකොට අලුත් line එකකට යන එක තමා වෙන්නේ. මේක අපි set කලේ නැත්නම් අපේ Multiline Textbox එකේ Enter key එක press කලාට මොනවත් වෙන්නේ නෑ.

TextWrapping Property එක Wrap කියල set කලාම අපි TextBox එකේ type කරගෙන යද්දී කෙලවරට අවම ඉබේම පහල line ඒකට cursor එක යනවා.

ඉතින් ඔන්න ඔය විදියට තම අපි WPF වලදී Multiline Textbox එකක් හදාගන්නේ. ඔයාලත් කරලා බලන්න.

උපුටා ගැනීම : http://msdn.microsoft.com/en-us/library/ms742157.aspx

Comments

Popular posts from this blog

Adding Unique Constraints with Entity Framework Code First

Entity Framework Code First is a great way to define and maintain your database within your application it self. While it poses a nice set of complementing libraries like Data Annotations and Fluent Configurations which helps you specially in defining phase of your database, it would give you a headache if you try to define a unique constraint on a column. For example in the users table of your application you could probably have an int ID column which would serve as the primary key and you might need to make your Username column a unique one. Since you are using EF Code First you will soon find out there is no direct way to accomplish this requirement. Unfortunately fluent configurations doesn't have syntax like HasUnique(u => u.Username); I asked the same question in stackoverflow , but didn't get a convincing answer. Since there is no direct support from EF for this you could take one of following alternatives to achieve it. Approach 1 :  

The list of do's and don'ts when preparing your resume

During past couple of years many times I was asked by my colleagues in the HR department "Could you please shortlist these resumes for interviews?" answer was almost always yes. As a result I have gone through a large number of resumes to check whether if these people are suitable for an interview.  While I'm scanning these resumes I found many reasons that I could reject these let alone the technical incompetencies of the candidates. Then suddenly one day I said to myself "why don't you write simple blog post about this?". So here I'm trying to put up a list of reasons that your resume might get rejected and how to minimize it. When you read this you will realize how trivial some mistakes are but they could surely cost your chance of landing your dream job. Typos in the resume Well I hate typos because it shows you how inconsiderate you are, keep in mind your resume is the first contact point with your potential employer so why don't

Building Highly Scalable Web Applications with Windows Azure

Among many other benefits of moving or building your web applications in cloud, for me I think the most important benefit we get is scalability. When it comes to web applications there are two approaches for scalability. Scale out - This means we increase the number of running instances of the application with a load balancer which distributes the requests among those instances Scale up - This means we increase the physical resources on a single application instance, for example we can increase the RAM of the hosted machine In reality preferred way of web application scalability should be to scale out. Because there are obvious hardware limitations in scale up approach. Bearing that in mind if we look at what Windows Azure provides out of the box, for a certain level it supports scale up approach and it has a great amount of support for scale out approach. Scaling your application out Windows Azure supports both automatic and manual scale out of the application.