|
My Vietnam
I write kernel os.Lam stars using VC6 write kernel and load it.
How to create _asm graphics.h for this kernel and use it in Vc6
by:tuan1111
|
|
|
|
|
Could you please make a more clear request?
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
Hello,
I have one problem with two different projects created in VS2003 and VS2005.
First of all I have a MFC extension dll in one project created in VS 2005. When we load this dll through test project created in VS 2005, everything is fine.
Now we need to use this same dll in one of the application created earlier using VS2003. In this application there is one mediator dll which I have compiled in VS 2005 and connected the previous MFC dll to this app.
After this if I do only
LoadLibrary(...) and
FreeLibray(..) immediately;
the VS2005 shows memory leaks in MFC dll before it unloads it.
What should I do?
Can program Money?
|
|
|
|
|
Dynamic linking mixed versions of MFC is an iffy proposition at best.
Anyone who thinks he has a better idea of what's good for people than people do is a swine.
- P.J. O'Rourke
|
|
|
|
|
Very right. I came out of iffy position after I made few changes and compiled the complete application projects in 2003 and then linked them to existing 2003 app. Believe it everything is correct and I have the project ready.
Can program Money?
|
|
|
|
|
Hello
Can anyone tell me like the things to be taken care of, while moving to UNICODE format, because the application am working is going to be supported in multiple languages?
while using functions like strcpy_s, do i need to be more specific about the size_t parameter?
that is, while doing a copy, do i need to specifiy more memory?
Thanks in advance.
|
|
|
|
|
Use the tchar equivalents of the str* functions, and wrap your string constants in the _T macro. As for the size_t parameter you can leave it as is as they refer to the number of characters in the buffer, not the number of bytes. As was said earlier, RTM.
You may be right
I may be crazy
-- Billy Joel --
Within you lies the power for good - Use it!
|
|
|
|
|
To add to the above; go to the documentation for the string calls. Scroll down. The remarks section will contain a list of what the equivalent tchar routine to use that will map to either the ANSI or UNICODE version of functions. So, the equivalent of strcpy_s is _tcscpy_s.
The second parameter of strcpy_s is the number of characters in the destination buffer. If you have a static buffer (i.e. TCHAR buffer[16] ) and are using sizeof(buffer) , you'll have to modify it to use sizeof(buffer) / sizeof(TCHAR) (in VS 2005 you can, as was already clearly pointed out below, use _countof(buffer) .)
dipuks wrote: that is, while doing a copy, do i need to specifiy more memory?
It depends on how you are allocating that memory. If you use TCHAR when allocating, then you're fine.
BTW, if using the defines LPCSTR & LPSTR, change them to LPCTSTR & LPTSTR. Most of these will be flagged when you compile with UNICODE.
Anyone who thinks he has a better idea of what's good for people than people do is a swine.
- P.J. O'Rourke
modified on Wednesday, June 24, 2009 11:53 PM
|
|
|
|
|
I learned MFC before, finally I gave up completely.
then now much more easier way than MFC exists, then I really do not understand why MFC
is still used? what is the advantage then?, let us say, compared to .net. Mainly due to its efficiency? but my experience told me that it is really not make progress in MFC.
thanks
modified on Wednesday, June 24, 2009 4:47 PM
|
|
|
|
|
1) There are still places where the .NET framework isn't widely installed, so .NET apps aren't an option (I know, I work at one)
2) I would say that MFC still has a better developed application framework than (say) Windows Forms - things like UI updating just seem better in MFC, IMO.
If you're going to use something instead of MFC, use Qt - that's a really nice UI framework, IMO - or (maybe) WTL - MFC-esque but lighter weight and (IMO) some things are nicer.
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
MFC has a more complete application framework. For example, the menu handling and tying menu items to button bar buttons.
Once you understand MFC and Visual Studio, it is very easy to rapidly create applications.
MFC has a massively huge amount of third party resources for it. CodeJock, for example, is an excellent UI interface (far better, IMO, than the BCG stuff Microsoft used for the 2008 Feature Pack.)
With few exceptions, MFC lets you seamlessly move between native Win32 and the framework.
MFC/Native applications [can] use much less memory than .NET applications.
MFC did languish for several years, then Microsoft did some actual research of actual developers and found that as of 2003/2004, 80% of client application developers world wide was still using MFC. As a result, they are paying attention again and for 2010 are allegedly adding back the fabulous Class Wizard from Visual C++ 6 and before. As for efficiencies; due largely to the heavy amount of COM added, it's become more bloated, but it's hard to make it much more efficient without changing the design (and even then, for large applications, the difference would be negligible.)
At one point WTL showed promise, but it was rather confusing and time consuming to create window classes. Unfortunately, rather than add some Wizards and beef up support, Microsoft threw WTL into the public domain. (Shame since I have shipping applets which could have been main leaner with WTL.)
Many (please note that I didn't say all) developers I personally know who claim .NET is superior to MFC were never very good at MFC; they never bothered to really learn it or Win32. Most of those are just as bad at .NET too; they just think they aren't. I use native Win32, MFC, and .NET. Many things are easier in .NET, some things are harder and some things are so blasted hard, it's just not worth it. There are some really nice things about .NET and C#, but when all is said and done, I'm a C/C++ programmer at heart. (Having said all that; anyone who needs to do web development or pure database front ends would be crazy to pick C++ over .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
|
|
|
|
|
Hi,
May i know how can i create a Slider Control with three ranges...ie
1--------2---------3
based on the movement ie if the slider is at 1 i need to display a static text as low(and need to set some registry also)and if 2 it should display medium AND 3 as high..
Please let me know regarding the same...
|
|
|
|
|
So what exactly is the problem? Have you called the SetRange(1, 3, TRUE) method, or sent the control a TBM_SETRANGE message?
"Old age is like a bank account. You withdraw later in life what you have deposited along the way." - Unknown
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
|
|
|
|
|
Hello all,
I am having problems with opening a device defined serial port using basic CreateFile function. The serial port is specific to a framegrabber installed in the PC. I can open and communicate with it with no problems in windows hyper terminal and evne in Matlab, but not able to open it in VC++. Usually with other framegrabber I can see all the additional com ports installed by the framgrabber under COM&LPT ports in device manager, but not with this board. But in registry under HKLM\HARDWARE\DEVICEMAP\SERIALCOMM, I see these ports listed.
The port names are not as usual COM1 etc, its with X64-CL_iPro_1_Serial_0/X64-CL_iPro_1_Serial_1 names.
Can anyone help me out here.... or does anyone know how windows hyper terminal opens these ports..
thanks,
PKNT
|
|
|
|
|
Hi
I am using something like,
char des[10];
char src[2] = "Hello";
strcpy(des, sizeof(des), src);
Because this application is going to be internationalized, i want WCHAR or UNICODE format implemented.
So will that make any change to calling sizeof(des)?
Do i need to do soemthing like, sizeof(des) * sizeof(char) ??
|
|
|
|
|
wchar_t buf1[80], buf2[80];
wcscpy_s(buf1, _countof(buf1), buf2);
You might want to read the documentation[^]
|
|
|
|
|
led mike wrote: You might want to read the documentation[^]
That's optional, isn't that?
It is a crappy thing, but it's life -^ Carlo Pallini
|
|
|
|
|
Of course! Many developers just wave their magic wand keyboard at the problem.
|
|
|
|
|
Hello I am working on some code and came across this
void *orpGetValue(char *key, SceSize *key_size)
{
void *value = NULL;
.....
.....
by using the void with the * infront of the name, the code will allow the passing of a pointer
that will allow the calling routine to assigned it to any variable type.
What is this called, I have been googling and can not find any info.
I know it is commonly used.
Thank you in advance.
|
|
|
|
|
|
Does the * refer to it is a pointer to a VOID and that the return can be used to reference an int or a string?
I googled kludge, but didn't see any C references to it
|
|
|
|
|
it's sometimes called a "generic" pointer. the caller is expected to know what the pointer is really pointing to.
|
|
|
|
|
Thank you!
I googled it and have found lots of info now.
|
|
|
|
|
I'd call it type-erasure really. You're removing all semblance of type information...
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
I would like to create a template class that takes two template parameters:
1) A typename parameter, T
2) A pointer to a template function, F, that has the following declaration
template<typename U>
U DoSomething(int arg) { ... } With such a declaration, I would like to instantiate my template class as follows:
MyTemplateClass<int, &DoSomething<SomeType>> myInstance; Is there some way to declare MyTemplateClass such that I can infer the typename of SomeType? I have tried the following two cases but receive a compile error for both:
template<typename T, template <typename U> U (*F)(T)>
template<typename T, U (*F<typename U>)(T)> I know that I could add a third template parameter, but would prefer to avoid it if at all possible. Thanks for any assistance,
Sounds like somebody's got a case of the Mondays
-Jeff
|
|
|
|