|
spacing pattern is same, but my problem how to think the logic for the spacing like building a pyramid placed in four directions with some gap.1 pyramid each direction!!
|
|
|
|
|
Try drawing it out on a piece of graph paper and then seeing if you could use a bit of maths to solve each line. The big hint is that the gap in each line is predictable.
|
|
|
|
|
nope..
not helping a beginner!!
|
|
|
|
|
I'm sorry, but I am not going to do your homework for you. It does you no good if I do it because it doesn't teach you how to solve a problem, it merely shows that somebody with over 30 years experience knows how to solve it. That's not going to help you get a job, is it?
|
|
|
|
|
What size font would you like this code to be written in?
/ravi
|
|
|
|
|
Hello
How I can snap my window, for all windows ?
I need push button, and my Form must snap to task bar, after other windows must snap to my window. Only when all windows is maximized. I need auto-snap to edges. For others applications..
Sorry for my english, I still searching in google, but no result.
My english is low level, forgive me, when I write with errors.
|
|
|
|
|
That's not easy. Of course you could read every window position via COM but I think before I start to explain, you should try to snap you Window to the screen edges.
If I would explain, I could write the complete code and that would take some time for me. This ain't a question to be answered here with some tips.
Take a look at the Windows COM-Model (system32.dll and so on) there is everything you need, but you have it to workout on your own, if there are no examples in google.
You can't do it directly with C#, I think.
------------------------------
Author of Primary ROleplaying SysTem
How do I take my coffee? Black as midnight on a moonless night.
War doesn't determine who's right. War determines who's left.
|
|
|
|
|
I think you will need to enumerate all open windows and use SetWindowsPos. This is a job for P/Invoke.
|
|
|
|
|
Hi, I was found solution. Looks good. What you think about this ? This licence allow use in commercial apps ?  I think - yes, but I'm not sure 100%.
Align window:
C# does Shell, Part 3[^]
My english is low level, forgive me, when I write with errors.
|
|
|
|
|
I would say yes. These are the parts that cover this IMO:
(C) If you distribute any portion of the software, you must retain all copyright, patent, trademark, and attribution notices that are present in the software.
(D) If you distribute any portion of the software in source code form, you may do so only under this license by including a complete copy of this license with your distribution. If you distribute any portion of the software in compiled or object code form, you may only do so under a license that complies with this license.
So, in your licence, you must state that at least some parts are subject to Microsoft Public License (MS-PL), even if you don't want that licence yourself. If it's commercial, get the company lawyers to check it!
|
|
|
|
|
I need to integrate security access cord to cafeteria access controls. If anybody’s can help me. if you give sample code it’ll help to me
|
|
|
|
|
Nope. No idea what you're asking for there. It sounds like "Urgntz. Snd cdz", but you couldn't be that daft could you?
|
|
|
|
|
Pete O'Hanlon wrote: but you couldn't be that daft could you?
See OP's previous questions for the answer.
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
Richard MacCutchan wrote: See OP's previous questions for the answer
Not necessary, the screen name says it all.
|
|
|
|
|
As far as I understand it (and from your question that mightn't be very far) you want us to provide you with "sample*" [probably] low-level integration code between two [probably] proprietary systems. You aren't going to get very far in this task.
* normally this means code that can be copied and pasted and pass of one's own
|
|
|
|
|
You do realise that we know you work for Merrill Lynch don't you, and that we have your email address. How do you think your boss would feel if he read this message and realised you didn't know how to do your job?
|
|
|
|
|
I already emailed his boss 
"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus
|
|
|
|
|
I really wonder how come these guys go through the interview with such an amount of lethargic attitude.
Vasudevan Deepak Kumar
Personal Homepage
Tech Gossips
The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep!
|
|
|
|
|
Yes, I wonder the same as well.
"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus
|
|
|
|
|
I write as one who is little more than a novice. As of this writing, I have litte more that the concepts of namespace, class, methods, operators, operands. Although there is much more learning in my path I have a need to comprehend and ultimately create an API for a project. My thinking is that if I can actually do items necessary to such an interface my practical experience would be more memorable to me. As of this writing, I have read the entire Wikipedia primer... understanding about half of it.
Primarily, I would want to see reading appropriate to my level but also some exercises so as to demonstrate what does what. Hoping for someone's guidance for a series of correspondence that would be finite. Presently working with visual studio 2008 Team Suite.
|
|
|
|
|
mauricemcse wrote: Although there is much more learning in my path I have a need to comprehend and ultimately create an API for a project
Considering you said you are a little more than a novice, I wouldn't recommend goind into API design this early. Other members may confirm or refute my opinion though.
API design is hard, and takes a lot of time to master (if it can be mastered). First of all, you have to design a whole set of class interactions: how they are related, how they communicate to each other, design patterns which may or may not be applied to some or all of them.
Then it's the user's point of view, and that is the hardest of all. You have to put yourself in your user's shoes and think like one: How could you make your API easy to use? How could you make the vital things obvious, while not buzzing him with details? What defaults should you provide? What sensible defaults should you set? How is your API configured, and how easily configurable can you make it? Then comes the API documentation, so on and so forth.
In my opinion, you cannot create an API before you master the use of at least several major ones (.NET comes to mind, and then another example of a well-designed API - the Android Java API). Also, you cannot create an API without a deep understanding of OOP and its concepts - classes, interfaces, inheritance, overloading, the whole primer. That's maybe the thing of most paramount importance.
After doing your homework learning OOP and playing around with some big APIs, then you can start doing one yourself. Start small - a small math library for instance, with a broad design instead of a deep one (in this way you don't have to think a lot about class links). After that, you can go on and expand your possibilities and your views (incremental doctrine comes to mind).
I'm actually looking forward to see more experience members' opinion on this, may spark a nice discussion.
Full-fledged Java/.NET lover, full-fledged PHP hater.
Full-fledged Google/Microsoft lover, full-fledged Apple hater.
Full-fledged Skype lover, full-fledged YM hater.
|
|
|
|
|
I agree with Andrei, do not start with an API, think up a project that interests you, a hobby or something you have asome knowledge of. I had one novice build a dive log as his sport was scuba diving therefore he kn what he wanted. Start from there.
Design the data structures your want to work with then build your database (I am LOB centric so I always think database first) then decide on your interface and start designing that. All the while reading up on the aspects of developing you are working with.
I think there are a number of articles on the first steps to becoming a developer around - good luck
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I also saw you got downvoted. While this shouldn't have been posted in C# (I think it would have been better posted in Design and Architecture), I am willing to cut you some slack because I believe your question was valid, and well-formulated (something we don't see much around here).
Downvote countered
Full-fledged Java/.NET lover, full-fledged PHP hater.
Full-fledged Google/Microsoft lover, full-fledged Apple hater.
Full-fledged Skype lover, full-fledged YM hater.
|
|
|
|
|
As the others said an API might be to soon.
If you want to learn and understand better, I would try to master the English language better first.
Don't get me wrong, you clearly did an effort to make yourself understandable, but the text does more resemble a google translate than really understanding the language. Understanding English better will make you understand the articles/tutorials better and will give you a broather range of resources to search for.
V.
|
|
|
|
|
First of all, welcome to the world of programming. I hope that the negative votes won't put you off.
Unfortunately, you have a lot of work ahead of you getting to understand the basics of programming in .NET. This is far too big an area for you to skip, and no one is likely to offer to enter into correspondence with you to teach you how to do this. The brutal truth is that we are all busy people, and offering this level of tuition is a full time affair - saying that, there's no reason for you not to ask about specific things and people will try to help you here if they can.
I would suggest that you start off by reading something like Jon Skeet's C# in Depth[^] to get a good understanding of C#.
Finally - the API itself. Writing an API is hard. It's not simply a matter of slinging some methods together. A good API requires a deep understanding of how people are going to access your code, and how they are going to use it. This really is advanced stuff and I would steer clear of it if possible. If you must produce an API, make sure that you check every input to ensure that it is valid - the golden rule of API design is "trust nothing".
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
