seen from United Kingdom
seen from United States
seen from Pakistan
seen from China
seen from United Kingdom
seen from Russia
seen from Brazil
seen from Finland
seen from United Kingdom
seen from Malaysia
seen from South Korea
seen from United States
seen from Netherlands
seen from Czechia
seen from China
seen from France
seen from Malaysia
seen from United Kingdom
seen from Czechia
seen from China
How to Line Up Columns in C#
How to Line Up Columns in C#
Lining up columns in C# can be tricky. If you make a Console Application, all the columns will line up correctly if you use the string.format function.
However, when working with Windows Forms, lining up the columns is basically the same as lining up columns in a console app. But then why don’t columns line up then?
The simple reason being that you need to change the font style of the rich text…
View On WordPress
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
String format constructors
Recently I noticed that I had a class with a constructor that had a single string parameter. For discussion lets assume that the class looked something like this.
public class SomeException : Exception { public SomeException(string message) : base(message) { } }
In my code I found several calls that looked something like:
throw new SomeException(string.Format("Could not find {0} in {1}", item, container));
This is perfectly acceptable way of creating an object but I wanted something a little cleaner. I modified the constructor's signature to look more like the string.Format signature:
public class SomeException : Exception { public SomeException(string messageFormat, params string[] args) : base(string.Format(messageFormat, args)) { } }
This then changes the previous constructor call to:
throw new SomeException("Could not find {0} in {1}", item, container);
It may not be as obvious that the constructor is doing a string.Format on the parameters, but I don't think it that far of a stretch for another program to see what is happening in the code.
String Formatting Mayhem
Apparently a pretty versatile template system. Now, I've used a couple in various different projects: Erb in my Rails, Jade in my feeble attempt at Node.js. But the situation I always find myself in is that often times, the templating markup usually clutters the main markup. Take this for example: <% @projects.each do |project| %> <%= project.name %> <%= project.due_date %> <% end %> There's _more_ template than there is actual markup! Not to mention, mixing <% %> with the html traditional < /> is **really** confusing to the eyes. This led me to something I thought about today... In the .NET world, you will often find something like: String.format("The answer is {0} miles", 123) This is a fairly flexible way of handling dynamic, potentially runtime string interpolation. Instead of passing '123' as a parameter we could call on an object. p = new Pedometer(); print(String.format("The distance from here to San Diego is {0}", p.from("53703").to("92101"))); I really like the flexibility of this, but why do the arguments even have to be positional. If you're scoping these formatted strings to an object, couldn't you just access attributes of an object directly in the string? Consider this: user = { name: "Nick Radford", email: "[email protected]", location: "Madison, Wi" }; str = "Welcome {name}, thank you for signing up with your email,"; str += "{email}. We noticed you're in {location}.\n"; str += " Click /here/ to see some great deals!"; Then by extending the String class, we could call: str.evaluate(user); to produce the following output: "Welcome Nick Radford, thank you for signing up with your email, [email protected]. We noticed you're in Madison, Wi. Click /here/ to see some great deals!" I like this way of marking up my text so much, that I'm using it in something I'm developing for work.
