|
I have DirectX.Capture.dll from Brian Low . It is c#.net and i know vb.net can use its but i don't know
how can i use function in dll with c++.net .
|
|
|
|
|
Ask in the C++/CLI forum.
Anyone who thinks he has a better idea of what's good for people than people do is a swine.
- P.J. O'Rourke
|
|
|
|
|
Its c++.net or not if not see here[^]
|
|
|
|
|
if sb will be read /write my file , my program had the power that can gave a messagebox show message: do you allow some program read/write the file ?Then we control the file whether can be read/write .
thanks.
|
|
|
|
|
You want to watch a file, and block other programs from reading from or writing to it ?
Christian Graus - Microsoft MVP - C++
Metal Musings - Rex and my new metal blog
|
|
|
|
|
hallo everybady :
i am a bigginer in C++ und MFC.ich am using Visual C++ Compeler. can you help me with following problem? :
ich want to show a table by clicking an undermenu, that was inserted in a menu of mainmenu. for exsample :
action is a Menu in mainmenu. under that there is a menu named Add_Table.
my problem is ,that where can ich edit this table ? in Visual c++ or anywhere else ? also it lookslike for me imposible to show it under the Resourses Window , with ActivX Elements. doesnt it ? do you have a Sugesstion to me ?
thank you much more.
Burkut
|
|
|
|
|
First of all, I thought I was reading something from D Ali G, but that's Borat. Had to laugh, sorry. I took German in high school, so could translate the ich and unds.
Anyway, I was unclear about what you are trying to do. Are you trying to pull up a view that shows a grid control so you can edit a database table?
I think we need A LOT more information before anyone can answer your question.
- S
50 cups of coffee and you know it's on!
|
|
|
|
|
well, Steve , yes i am seeing my mistake too. it is really to laugh. what can i do, my english is poor enough. i know it. i make sometimes like this mistakes. ha hahahah ... but i will try to interpret my problem more specificly ...
otherway way you have understand this problem somewhat. i am trying to pull
up a view that shows a grid control so you can edit a database table, this table should be zoomed in or zommed out at any time. for example: the grid distance is 100 Mikrometer. i want the grid distance smalleror bigger by zooming. in a wort , ich don't want to make a statische grid , but a dynamische grid.
the zooming of the grid should be controlled by buttons ZoomIn/ZoomOut for example.
my question was that how can i get this grid? should i impliment a funktion that paint the grid or , is there an vordefined funktions or classes? if not, i want an Idea, how do i get the grid?
thank you for your time and your understandings of my problem.
burkut
|
|
|
|
|
Can you be more specific.
|
|
|
|
|
well, yes i am seeing my mistake too. it is really to laugh. what can i do, my english is poor enough. i know it. i make sometimes like this mistakes. ha hahahah ... but i will try to interpret my problem more specificly ...
otherway way you have understand this problem somewhat. i am trying to pull
up a view that shows a grid control so you can edit a database table, this table should be zoomed in or zommed out at any time. for example: the grid distance is 100 Mikrometer. i want the grid distance smalleror bigger by zooming. in a wort , ich don't want to make a statische grid , but a dynamische grid.
the zooming of the grid should be controlled by buttons ZoomIn/ZoomOut for example.
my question was that how can i get this grid? should i impliment a funktion that paint the grid or , is there an vordefined funktions or classes? if not, i want an Idea, how do i get the grid?
thank you for your time and your understandings of my problem.
burkut
|
|
|
|
|
Hi there guys, I am currently trying to achieve a seemingly simple task in VC++ 2005. I have made a very simple form in Microsoft Access which I wish to serve as the beginnings of something greater. I created a db in MS Access named links.mdb containing on table-> Table1. Table1 contains 1 column, "Links", and i wish to read these strings into variables in my Visual C++ Windows Forms Application.
What I have done so far...
In Visual C++, I clicked on Data->Add new data source, and followed the wizard to add the microsoft access database to my application by the name, "linksDataSet". I can see the table in my left hand "Data Sources" pane in VC++. All I need to know is how to access my database from here so that I can read these strings stored in my table. Also, would be possible to schedule my application to log on to a http server and retrieve these links every time the application is executed? How would I go about doing this?
Thank you very much for your time
Regards
Linden.
|
|
|
|
|
17hrs and not one reply? Patience is a virtue but this seems like a small task. Can anyone help me?
|
|
|
|
|
I notice that in C# I can very easily design the UI.
I am familiar with the differences between the two, except for one thing.
I am about to write an app that could be written in either, but will interact with .dll's written in C/C++, which means I'd rather write it in C++. But, I am wondering if all of the UI elements are available to me in C++, like toolStrips for example.
Should I buy a good book on Win32?
Patrick
|
|
|
|
|
You have two main choices; MFC or WTL. WTL will give you a smaller executable and a lot of low-level control. MFC will be larger and require you use one of a few frameworks. On the other hand, you will be able to program much faster in MFC, especially since VS has many wizards built in. MFC also has the advantage of many third party libraries and solid documentation. (WTL documentation sucks big time.)
Unless you've built of the proverbial bag o' trick in ATL/WTL, I'd recommend using MFC.
One thing to remember for any native Win32 programming is that there is a strong separation of UI and implementation (something which drives us native guys nuts when going to .NET.) In other words, you dialog box is created using a data set and can be changed quite independently of the code (which is how it should be; XAML is an attempt to fix this in .NET.)
Anyone who thinks he has a better idea of what's good for people than people do is a swine.
- P.J. O'Rourke
|
|
|
|
|
C# will definately give you a richer UI. You can use C++/CLI to create a bridge between C# and C++
Christian Graus - Microsoft MVP - C++
Metal Musings - Rex and my new metal blog
|
|
|
|
|
Hi everybody
Being a c++ coder for so long, i should not make this question... but ei... it dosen't hurt.
I have become aware of a serius problem on one medium project. To many rebuilds
I have to many files (that need to be changed often) fireing to many outher files to rebuild.
Imagine the pain... I know its a design problem, and i preparing miself to a major rework.
However, i was thinking if someone could redirect me to a good article on this topic before i get my hands on the problem.
Where can i find the "What to do... and What not to do..." stuff?
I am trying to complement my knoledge on this.
Thanks
-- modified at 13:58 Monday 14th August, 2006
|
|
|
|
|
So what is your question, exactly?
"Money talks. When my money starts to talk, I get a bill to shut it up." - Frank
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
Hi.
The question is , where cant i get more information on this topic?
The "What to do... and What not to do..." stuff 
Thanks
|
|
|
|
|
Max Santos wrote: The question is , where cant i get more information on this topic?
I don't suspect you'll find much about it from CNN.
Max Santos wrote: The "What to do... and What not to do..." stuff
The brute-force method involves commenting out one #include directive at a time and rebuilding. If it builds successfully, you know that that #include directive is not required.
"Money talks. When my money starts to talk, I get a bill to shut it up." - Frank
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
DavidCrow wrote: The brute-force method involves commenting out one #include directive at a time and rebuilding. If it builds successfully, you know that that #include directive is not required.
Yeap, but before i go shooting everyone of the 370 header files, i would like to read something good before trying to aim.
|
|
|
|
|
The question would seem to be, "How do I minimize dependencies". It's clear enough in the post.
Steve
|
|
|
|
|
I always like "Large Scale C++ Software Design" by John Lakos; it has a couple of good chapters that talks about compile and link time dependencies.
|
|
|
|
|
thanks for the tip.
i went to amazon.com but the book is temporarily unavailable 
|
|
|
|
|
To be blunt, a book is a giant waste of time. Take a cut of your project and start experimenting. You will learn far more in a week of deliberate tests than in reading all the books you can find. It's a whole lot cheaper too.
(I speak from experience; I have been the build engineer on many projects and have always improved them measurably.)
Anyone who thinks he has a better idea of what's good for people than people do is a swine.
- P.J. O'Rourke
|
|
|
|
|
Here's a set of techniques in order of increasing risk and diminishing returns:
Start in StdAfx.h, assuming you're using precompiled headers (and the precompiled header has the default configuration; if you're using a different header for PCH, edit that instead). Leave only #includes in this file which are stable (e.g. dependencies on external libraries) or which really do need to be included in absolutely every file. I often see StdAfx.h used as a dumping ground for all headers in a project, which, since all source files include StdAfx.h, causes every file to be recompiled even if a tiny change to an inconsequential header occurs.
If you're not using precompiled headers, consider doing so. The amount of time taken to parse <windows.h> is huge because it includes most of the files in the Platform SDK Include directory, which as of VS2005 is 46MB. MFC and ATL headers include windows.h.
Once you've edited down StdAfx.h, you'll probably have a load of compilation errors. Just get it to compile for now, by including only those headers you actually need. For class members, in the header, forward-declare those classes which are only referenced by pointer or by reference; #include those which you must.
In each header, look for uses of classes and structs defined outside that header. If a class only appears in pointer and/or reference declarations, it can be forward-declared rather than the corresponding header being #included. The source file that actually implements the functions manipulating the pointer or reference will need to #include the header declaring the class.
Look out for implementation of methods in class declarations. These should be a) trivial and b) stable, and ideally not reference the implementation of other classes. Any that aren't should be stripped out and placed in a source file. Method implementations in class declarations have the additional semantics of being considered for inlining. Generally you can get away with not inlining most of this code with very little performance impact. MFC uses a trick of keeping performance-critical routines in files with a .inl extension: in debug builds, the matching _AFXxxx_INLINE macro expands to nothing and the file is #included in the corresponding .cpp file, while in release builds the macro expands to inline and the file is #included in the corresponding header, which causes the code to be inlined if required.
If an otherwise stable class has a class member which is unstable (the declaration constantly changing), consider changing it from being a contained member to a pointer to that class, then forward-declare that class and remove the #include.
Consider replacing parameters of class or struct type with a const reference. This also saves a call to the copy constructor.
Look for overuse of inheritance. When inheriting, the full declaration of a base class is required at the point of declaration of a derived class. If the base class implementation details change, it will impact all the derived classes. It may be better to declare an abstract class containing only the public interface, and derive concrete classes from the interfaces. Often inheritance is used unnecessarily, and composition - reimplementing the derived class in terms of its former base class - is a better technique.
If you don't want to incur the overhead of virtual functions when trying to hide the implementation details of a class (for example, there would otherwise not be any virtual functions), consider the so-called 'pimpl idiom'. Here you move all members that are unstable into a separate 'implementation' class, then replace all those members in the original class with a single 'pointer-to-implementation' member.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
