|
Hehehehehehe!
Its the man, not the machine - Chuck Yeager
If at first you don't succeed... get a better publicist
If the final destination is death, then we should enjoy every second of the journey.
|
|
|
|
|
Mehdi Gholam wrote: I have found them indispensable
As long as they are used carefully and in a limited way.
|
|
|
|
|
I agree passing large objects around with them is a bad idea.
Its the man, not the machine - Chuck Yeager
If at first you don't succeed... get a better publicist
If the final destination is death, then we should enjoy every second of the journey.
|
|
|
|
|
|
I want to upload a file on my web page with httpwebreqest
<title>kilo
|
|
|
|
|
Is this a question that needs an answer? If so, then please explain what problems you are having: "I want to" does not really tell us anything.
|
|
|
|
|
|
Go ahead
My number one dev tool? Google
|
|
|
|
|
Use the resizing handle at the bottom right corner of the dialog.
|
|
|
|
|
I didnt understand your question correct.
Do you want to resize dialog using program code in some of the programming languages , or ...
To resize an open window:
To change the width, point to the left or right window border. When the pointer changes into a horizontal double-headed arrow , drag the border to the right or left.
To change the height, point to the top or bottom window border. When the pointer changes into a vertical double-headed arrow , drag the border up or down.
To change the height and width at the same time, point to any window corner. When the pointer changes into a diagonal double-headed arrow , drag the border in any direction.
Note
You cannot resize a window when it is displayed in a full screen (maximized).
If you need code ( C# ) for resizing dialog please reply to this message.
PS.
If you are creating program ,(based on the pictures you send),
in some of the visual tools ,use the properties in design mode for the wanted dialog (it seems that it is openFileDialog), where you usually can change the size of the dialog (Hight ,Width ) , it depends on what kind of programming tool you are using.
All the best,
Peric Zeljko
periczeljkosmederevo@yahoo.com
|
|
|
|
|
Trying to start learning and using the dotnetnuke .net framework with CMS to build a website.
I have used .Net framework to build web application using visual studio 2010.
What are key features and where can I learn more about it?
Looking for advice to get started.
|
|
|
|
|
|
Where go I to find about a search engine?
Pleas help and thanks many in advanc.
|
|
|
|
|
Go hire a detective; if you find said engine, please let us know.
|
|
|
|
|
Hello fellow programmers.
I would like some advice about comments. I am not asking about how to comment a particular line of code, but rather the comments that precedes a function, class, interface, or etc and how to describe it such that other programmers can quickly understand what it's all about.
The reason why I ask is if I am missing out on some creative way of documenting my code. I understand that I need a brief description of the object that I am creating along with a description of what each parameter (if any) and the return value (if any), but I am wondering is there something else that I am missing.
My question to all of you is what type of style of commenting does your work place enforce or what is your favorite style of commenting that you came up with?
Thanks in advance!
|
|
|
|
|
There is no particular style to writing comments. Just think of yourself looking at the code for the first time, what information would you like to see? Comments don't need to be paragraphs of information, just straight to the point with an example usage perhaps. Longer descriptions and explanations can be applied in other forms of documentation.
No comment
|
|
|
|
|
Thanks Mark,
I figured as much, but was just curious to see how others have dealt with this. You make a good point about the longer descriptions can be placed in other forms of documentation.
|
|
|
|
|
Name your functions, parameters and variables with self describing names and a lot of the documentation will be done for you. It's called self-documenting code.
That doesn't relieve you of the responsibility of describing what a method's purpose is and what you're trying to accomplish.
Also, I hate comments that say what you are doing (like, "iterate over customer list, printing invoice", or "declare local variables") -- I can read the code for that. Tell me *why* you're doing what you're doing, especially if it's not obvious.
If your actions inspire others to dream more, learn more, do more and become more, you are a leader." - John Quincy Adams
You must accept one of two basic premises: Either we are alone in the universe, or we are not alone in the universe. And either way, the implications are staggering” - Wernher von Braun
|
|
|
|
|
Ahmed,
Thanks for your response. You make a good point about describing the purpose of the piece of code. That is also something that I have been considering.
|
|
|
|
|
Clark Kent123 wrote: The reason why I ask is if I am missing out on some creative way of documenting my code.
Drop the creative, go for structured and standard. Commenting code has it's section in the manual[^], and following it gives a few benefits (thanks to the integration with VS).
Pick a method, put your cursor on the line above it, and type three forward slashes if you're in C#, three quotes if you're in VB - the IDE will generate a template and you'll only have to fill in the blanks.
Clark Kent123 wrote: what is your favorite style of commenting that you came up with?
I tend to skip these creative discussions altogether and just reuse what Microsoft used. Same goes for variable-naming; choosing between Apps Hungarian or Systems Hungarian is a waste of time.
|
|
|
|
|
Perhaps you missed this from the OP
Clark Kent123 wrote: I am not asking about how to comment a particular line of code,
No comment
|
|
|
|
|
Mark Nischalke wrote: Perhaps you missed this from the OP
Clark Kent123 wrote: I am not asking about how to comment a particular line of code,
I did not miss it.
It applies to things as classes, properties, methods and fields. It's an advice on it's structure, not it's contents. I do not see the OP asking for any specifics
Bastard Programmer from Hell 
|
|
|
|
|
Eddy Vluggen wrote: Pick a method, put your cursor on the line above it, and type three forward slashes if you're in C#, three quotes if you're in VB - the IDE will generate a template and you'll only have to fill in the blanks
"In Visual C# you can create documentation for your code by..."
Seems a bit "How To" to me
No comment
|
|
|
|
|
Mark Nischalke wrote: Seems a bit "How To" to me
True, but ain't limited to a "single line" as the TS said
Bastard Programmer from Hell
|
|
|
|
|
Type /// on top of a method or class.
You will automatically get the method name, arguments and return value automatically.
This is very useful because this will then help you focus on only those items that are relevant enough to be commented on.
Too much of heaven can bring you underground
Heaven can always turn around
Too much of heaven, our life is all hell bound
Heaven, the kill that makes no sound
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
