|
And what do you think about writing an application that will appeal to memory addresses that are present in the system 16
|
|
|
|
|
I don't see how that helps - what are you trying to achieve?
Bastard Programmer from Hell 
|
|
|
|
|
Because it just so happens that I have instructions from the camera. In intrukcji this is contained the description of setting memory addresses. I thought that maybe this way I can somehow tare camera. I will send you a CodeProject sample program from which memory addresses are used. If you have any idea how much it help me please help.
DirectShow.NET[^]
|
|
|
|
|
Sorry, that's too complex for me. AFAIK, Windows can relocate your code in memory without warning, meaning that the addresses change.
Doesn't the camera have an SDK?
Bastard Programmer from Hell
|
|
|
|
|
I will send you a page where there are cameras in the documentation of these cameras are available these registers.
Look at the Technical Manual
|
|
|
|
|
I only found references to memory inside the camera; I'm sorry, but I don't know much about hardware.
Bastard Programmer from Hell
|
|
|
|
|
|
When naming variables, do you use "filename" or "fileName"?
I find myself going back and forth, and can't get my mind to pick one and stick with it.
|
|
|
|
|
Use mixed case fileName, makes them much easier to read.
|
|
|
|
|
Actually, in this case I find filename easier to read than fileName.
|
|
|
|
|
filename.
However, in public APIs, I name properties FileName and UserName in keeping with Microsoft's convention.
/ravi
|
|
|
|
|
Properties would start with a capital-letter, but a variable wouldn't 
Locals are usually Pascal-cased.
Bastard Programmer from Hell
|
|
|
|
|
Yes, I know. I was referring to the case of the letters within the identifier. I thought that was blindingly obvious.
/ravi
|
|
|
|
|
With programmers, nothing is "obvious" unless it's in the specs. I assumed that everyone would simply follow the guidelines from Microsoft, making this a non-question.
Bastard Programmer from Hell
|
|
|
|
|
Probably a dumb question, but where can I find the Microsoft guidelines for this? 
|
|
|
|
|
Caydence wrote: Probably a dumb question
It's not, but I'm glad to see that you rather make a "dumb" impression and get an answer than look intelligent and move on without one.
Here they are[^]
Bastard Programmer from Hell
|
|
|
|
|
I don't mind admitting I don't know something.
|
|
|
|
|
|
VS' Code Analysis' built-in dictionary checks your identifiers for spelling, grammatical case and other naming conventions of the .NET Framework guidelines. It's a great a way to gets started, and it's easy to modify/override spellings and naming conventions where necessary.
/ravi
|
|
|
|
|
Eddy Vluggen wrote: the guidelines from Microsoft
So, ummm... explain why Hashtable and DataTable don't agree.
|
|
|
|
|
I'm not an employee, and I didn't claim it was consistent. It is however, always a good starting place for ideas, and a good place to end discussions.
Bastard Programmer from Hell 
|
|
|
|
|
That's because one is a republican and the other, a democrat.
|
|
|
|
|
Mostly filename
But that's because I had to forcibly break myself of using strFilename...
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
|
|
|
|
|
Did you used to have lots of lngFilename or blnFilenames as well? 
Bastard Programmer from Hell
|
|
|
|
|
I saw a variable declared as longAss. Ass was short for assignment no.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
