|
Thank you for your entries!
Meanwhile, i have struggled with this stuff (somehow
it felt familiar in a worrying way).
My real problem with this wouldn't be wether the methods
showed up or not, it was merely a symptom in line with was
bothering me: I could not _access_ the methods either (from
the DerivedLists) - maybe I should have mentioned that, too.
What I was doing was of course that I 1st hadn't defined the
functions, so I wasn't worried about not being able to use them
at that point. I just wrote them BUT! (moan) I placed them in a
.cpp-file of their own. So they weren't visible or what the
term is (and still not showing in the Class view), and I just
got complaints of unresolved externals for them when linking.
It was a year ago (but under some command line compiler) I did
battle a while with some template things and for the 1st time
realized I should place the template class' member functions
in the same file. This was my 2nd revelation. Hope I need no 3rd 
Thanks again for your input!
Regards
/Petter
|
|
|
|
|
Hi everyone. I have an MFC app which usesDAO to access Jet/Access databases. The development machine is Win2000 sp3 with Visual Studio 6 installed. The app is statically linked so MFC DLL version conflicts shouldn't be an isue. The app works 100% of my development machine, but I tried it on a Win98se machine and it won't open a Jet database file. The Win98se machine has DCOM98 and MDAC 2.5 installed on it, and only necessary software installed. Only my app is running whne I tested it. The app runs fine until I attempt to open a database. The code below is how I open the database
<br />
CDaoDatabase* db;<br />
CEDaoRecordset* rs;<br />
CString strSQL;<br />
long int lTemp;<br />
<br />
try<br />
{<br />
db = new CDaoDatabase();<br />
db->Open(strDBPath, FALSE, TRUE, _T(";PWD="));<br />
rs = new CEDaoRecordset(db);<br />
<br />
strDBPath is the path to the DB Jet database file, which is known to be valid, and not read-only.
Once it hits db->Open() I get an "unknown exception" error and the program closes.
I know it could be anything, but does anyone have any ideas as to what could cause this? Did I forget to install something? The app is MBCS based, not unicode.
|
|
|
|
|
Have you caught the exception and analyzed it? You should be able to get detailed error information if you use try{}catch{} and take a look at the error codes being returned.
Are you 100% sure that the database itself was copied over exactly? If both machines are trying to access the same DB, then you may want to look at the DB driver versions installed on each machine. Your development platform may be using different drivers.
|
|
|
|
|
I am making a small Win32 API application. I wanted to have a coloured background. When I tried to handle WM_ERASEBKGND, I got too much flicker. I tried to make a memory dc and use it, but that did not improve the flicker. Is it something I do wrong? Could you please show me how to handle WM_ERASEBKGND without flicker?
Note: I noticed that the flicker was gone when I created a brush and made myWndClass.hbrBackground point to it. But the problem is that I may want to draw in WM_ERASEBKGND, not just have a single brush.
<marquee behavior="alternate">Hosam Aly Mahmoud
|
|
|
|
|
Do everything in response to WM_PAINT and use a memory DC. Handle WM_ERASEBKGND and do nothing there.
Hope this helps,
Ryan "Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
|
|
|
|
|
Thank you for your reply. I thought that WM_PAINT would only allow me to draw a certain region of the window, not all of it. Also, the docs said that to make a background (for example a picture) you should handle WM_ERASEBKGND. Am I wrong?
<marquee behavior="alternate">Hosam Aly Mahmoud
|
|
|
|
|
Hosam Aly Mahmoud wrote:
I thought that WM_PAINT would only allow me to draw a certain region of the window, not all of it.
The device context given as a parameter to a WM_PAINT message is set up to only draw to the regions of the window which have been invalidated. By definition, any region that is not invalidated, does not need painting, so you shouldn't have a problem.
Hosam Aly Mahmoud wrote:
Also, the docs said that to make a background (for example a picture) you should handle WM_ERASEBKGND. Am I wrong?
WM_ERASEBKGND is sent whenever InvalidateRect() or InvalidateRgn() are called with fErase=TRUE. If the fErase flag is FALSE, then WM_ERASEBKGND is not sent. It is quite ok to draw the background in WM_PAINT however. In fact, to get true flicker-free drawing, it is the only way.
Ryan "Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
|
|
|
|
|
Many thanks for your reply. I am using Win32 API, so I get the HDC using BeginPaint(). I tried to draw in WM_PAINT, but I get a white background although I have myWndClass.hbrBackground = NULL. Here is my code:
case WM_PAINT:
{
static PAINTSTRUCT ps;
static dc = BeginPaint(hWnd, &ps);
static HDC memDC = CreateCompatibleDC(dc);
static HBITMAP memBitmap = CreateCompatibleBitmap(dc, MainWindowRect.right, MainWindowRect.bottom);
SelectObject(memDC, memBitmap);
FloodFill ( memDC, 20, 20, RGB(255,0,0) );
static HBRUSH oldBrush = (HBRUSH) SelectObject(memDC, myBrush);
Rectangle(memDC, myRect.left, myRect.top, myRect.right, myRect.bottom );
SelectObject(memDC, oldBrush);
BitBlt(dc, 0, 0, MainWindowRect.right, MainWindowRect.bottom,
memDC, 0, 0, SRCCOPY);
EndPaint(hWnd, &ps);
return 0;
}
case WM_ERASEBKGND:
return 0;
<marquee behavior="alternate">Hosam Aly Mahmoud
|
|
|
|
|
Remove the static keyword from all of your variable declarations and try again.
Ryan "Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
|
|
|
|
|
I did it but no difference. 
<marquee behavior="alternate">Hosam Aly Mahmoud
|
|
|
|
|
Hosam Aly Mahmoud wrote:
FloodFill ( memDC, 20, 20, RGB(255,0,0) ); // red background
 I should have seen this before...
The colour you pass to FloodFill() is not the colour of the fill. It's the colour of the border. FloodFill() fills the area with the currently selected brush. To fill a rectangle with a given colour, either create a solid brush (CreateSolidBrush()) and use Rectangle(), or use the ExtTextOut() function to draw opaque text without actually drawing text:
SetBkColor(memDC, RGB(255,0,0));
RECT rect;
ExtTextOut(memDC, 0, 0, ETO_OPAQUE, rect, NULL, 0, NULL); Hope this helps,
Ryan "Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
|
|
|
|
|
Thank you very much! That really helped! 
Now I am wondering, if I want to make the background an image, should I do it in response to WM_PAINT too? Why is WM_ERASEBKGND available then? Why did they put it if I should draw in WM_PAINT?
Thank you very much for your patience! ![Rose | [Rose]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/rose.gif)
<marquee behavior="alternate">Hosam Aly Mahmoud
|
|
|
|
|
Hosam Aly Mahmoud wrote:
Now I am wondering, if I want to make the background an image, should I do it in response to WM_PAINT too?
Yes. That will work fine
Hosam Aly Mahmoud wrote:
Why is WM_ERASEBKGND available then? Why did they put it if I should draw in WM_PAINT?
There is nothing wrong with using WM_ERASEBKGND for drawing the background. It's simply not possible to do flicker-free drawing using it. I'm not certain why it's there - it's probably been there since Windows 1.0
Ryan "Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
|
|
|
|
|
Ryan Binns wrote:
I'm not certain why it's there
Well, if you "eat" the WM_ERASEBKGND message, return 1, and forward it to the parent window, you can get transparent effects, because you're telling the parent to erase an area, rather than erasing it yourself with the default brush, which is the normal behavior.
This is a neat trick that is played by the Common Controls Toolbar so that it can have a transparent background. It also calls WM_ERASEBACKGND on the parent window whenever it draws anything outside of a WM_PAINT message, so that the background is always erased to the parent's background.
"Blessed are the peacemakers, for they shall be called sons of God." - Jesus
"You must be the change you wish to see in the world." - Mahatma Gandhi
|
|
|
|
|
 I'll have to remember that
Ryan "Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
|
|
|
|
|
Thank you for the information!
Hosam Aly Mahmoud
|
|
|
|
|
Thank you for your replies, your help and all your patience! ![Rose | [Rose]](https://www.codeproject.com/script/Forums/Images/rose.gif)
Hosam Aly Mahmoud
|
|
|
|
|
Hi,
I've written a program and when I run it for the first time it works, but when I want to run it for the second time, it crashes. Most of the time at a "delete [] ..." or at a "new char[...]". But when I debug it works fine.
The program uses a MySQL database (through MySQL++). Somewhere in the code is a "for()" part (it retrieves the records of a SQL-statement and does something with the values). When I debug it, it only goes one through the loop (retrieves one record), when I compile an optimized exe then it retrieves all the records.
I think this is very weird, does anybody knows the cause of the problem or has a sollution?
Thanks in advance
|
|
|
|
|
Sounds like an uninitialized variable somewhere.
- Mike
|
|
|
|
|
I see what you mean but how can something like this crash on "new ..."?
char* cNewString = NULL;
// cString is not empty
cNewString = new char[strlen(cString) + 1];
-Tom
|
|
|
|
|
Visual C++ is not perfect in reporting the cause of a crash and where the bug resides. One possible cause of delete [] is that the program passes the dynamically allocated array into a function that does not release the memory even after the function has returned.
Kuphryn
|
|
|
|
|
Probably a newbie question but I really want to ask, I have like hundreds of jpg's, gif's and icons need to be shared by multiple application, I heard we can encapsulate all of them into a dll and use that dll to export resource ID's when required by application, but how? Could someone please tell me:
1, what kind of dll I will need to create? Win32 dll? MFC dll? Or others?
2, How do I export resource ID's from a dll?
Thanks a lot.
|
|
|
|
|
putting hundreds of jpgs in a dll is a very bad idea, because it will waste your memory... you won't need them all the same time!
create a folder, put them in there, then create a new dll with 2 exported function: LoadJpg and FreeJpg!
LoadJpg allocates memory and loads the file from disk, FreeJpg frees the memory allocated by LoadJpg!
This is the best way!
Don't try it, just do it! 
|
|
|
|
|
Yeah I thought so, but I was just doing some practice, thanks for the suggestion though...
Anyway, I think I have found out the solution already, I created a DLL and included images into that DLL as its resources, then in my executable I read images("resource blocks") from the DLL into my executable process's memory blocks when needed, then draw them on my executable's windows, tested and worked.
|
|
|
|
|
use a normal win32 dll and include the resources there!
then load this dll via LoadLibrary!
now, you can open a bitmap for example by calling LoadBitmap with hInstance of the loaded dll!
Don't try it, just do it!
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
