|
Unless you are talking about large quantities of data I would just go with the structure idea.
Art
|
|
|
|
|
Not too large, in total there's about 60-70 ints and CStrings that I'll be needing to store (and maybe a CArray too). So it just seemed almost pointless to create so many files for so little data.
|
|
|
|
|
Hi,
I had an access violation in my MFC application. In the debug mode I saw the message in the Call Stack window as
Data_Write_winbuffer(void * 0x0012e9d4) line 494 + 22 bytes
KERNEL32! 77e802ed()
What does that "+ 22 bytes mean" ?
Can anyone help me out?
Thanks,
Deepak Samuel
|
|
|
|
|
It means that the error occurred at the instruction 22 bytes past the first instruction that was compiled for line 494 of the Data_Write_winbuffer function.
If you have a complicated expression on this line, you can either look at the disassembly for that line and try to work out from that where the problem occurred, or you can simplify the expression, recompile, and try again.
|
|
|
|
|
Hi all,
i like to made a Multidocument .exe where i have the mainframe window with a childwindow and as a second childwindow i like to load a .dll which creates its own dialog. So, how can i fit this upcoming dialog into the MainFrame window as nice as the other child window is fitted in it? I like to have the childwindow dialog at the left and the dll dialog on the right...
Thanks, Mark
|
|
|
|
|
I cannot give you a direct code implementation, but I will discuss shortly on how a MDI program handles it's child windows.
First, we have the frame window, derived from CMDIFrameWnd. Then, you have a set of CMDIChildWnd objects placed in there. The main frame window is a MDI Frame. The child windows function similarly as a CFrameWnd does, except they rarely have toolbar of their own.
So, when in SDI application, a Frame window has one view, then in MDI application, a frame window has many child frames, which each have their own views. Do you understand this ?
Following this logic, the easiest way would be to create a CMDIChildWnd object in the DLL, and create a Form View to fill this window's view. This way, you would have two valid MDI child windows, from which the first would have a normal view and the other one a form view.
I would follow this approach, because I am unsure how a modeless dialog works when it is a child of a MDI frame window. I have never tested it myself. But using the CMDIChildWnd->FormView approach would give valid, working results, as both child windows would then be CMDIChildWnd objects, and would have all the necessary implementation ready for functioning as MDI childs.
When the windows are created, you must position them appropriately using SetWindowPos member of CMDIChildWnd. Just get the client rectangle of the parent frame (CMDIFrameWnd::GetClientRect), divide it to half X-wise, and use these values to determine the size and position of both windows. First window should be from (0, 0) -> (X / 2, Y) and the other from (X / 2, 0) -> (X, Y), where X and Y are the width and height of the client area, respectively.
-Antti Keskinen
----------------------------------------------
The definition of impossible is strictly dependant
on what we think is possible.
|
|
|
|
|
Yep, thanks. But it is a thirdparty .dll. I don t know if there is an childframe obj in it. Maybe..
Thanks, Mark
|
|
|
|
|
How can i do a search in a DC? I need to determine if there's a certain set of pixels (another, much smaller DC) present in a big DC. How can i do this? I already did some searching on this site and on MSDN but i can't come up with anything usefull.
Thanks.
|
|
|
|
|
There is only one way: brute force
In an MFC implementation, you would use a CDC object and the GetPixel SDK function. The function returns the color of a pixel in the specified point.
You would need to run through the bigger DC in pieces of the smaller DC, comparing each pixel against other.
-Antti Keskinen
----------------------------------------------
The definition of impossible is strictly dependant
on what we think is possible.
|
|
|
|
|
Hi All,
I transparentize a window by SetWindowRgn, but I can't control it's alpha.
How to control it? Like SetLayeredWindowAttributes under Win2K.
I want to transparentize a window captured by WindowFromPoint
Thanks.
Xiaobin
|
|
|
|
|
Not doable.
The layered windows are only available in Win 2000/XP and later. You could attempt to creating a window, then making it's whole client area from an image that supports transparency, and paint the background of the window with a NULL brush. This, however, would require you to constantly erase and repaint the background.
Using this method with a WindowFromPoint would require you to subclass the target window, take a screenshot of it's DC, create an image from this DC that supports transparency, then set the background brush to NULL for the window, and repaint it completely with the transparent image.
In conclusion: impossible, get an OS version that supports layered windows or forget the idea 
-Antti Keskinen
----------------------------------------------
The definition of impossible is strictly dependant
on what we think is possible.
|
|
|
|
|
Hi Antti,
Thanks.
I get the address from SetLayeredWindowAttributes from "User32.dll" and set it to a function pointer. If the pointer is NULL, I set the IsW2K false.
I choose the transparent function in this way, am I right?
And, when I move a window transparentized in your method, it seems can't retain transparency. What shall I do?Hook the WM_PAINT message?Or...?
I wrote a program can make window captured transparency under Win2K, but I want it suport Win9x. I found it difficult. -.-;;
|
|
|
|
|
Well, like I mentioned, you can make a program that adds a transparency effect to a window under Win2k. That much is simple. If you want your program to not crash in Win9X, you need to check for the availability of SetLayeredWindowAttributes in User32.dll.
The method I described requires that you subclass the window, get it's class style and variables, then register a new window class with NULL brush and set this class as the window's class. Naturally you need some way to preserve the original window class so you can return it when your program exits.
When a window has NULL background brush, it's background gets painted with the desktop image currently underneath the window when the background is refreshed. You can force a window to redraw itself by issuing a RedrawWindow method call. Of course, you would need to order the window to refresh itself always when it is moved.
This isn't a very working method to force other process' windows go transparent, because you would then constantly need to handle WM_PAINT messages to capture the DC of the window to a transparent image, process it, and re-paint the window with the new image. This adds a big amount of overhead and will certainly slow the program's execution.
Transparency is just not supported on Windows 95/98. You can add transparency for Windows 2000/XP programs and make sure your program works correctly on 95/98 by fetching the address of SetLayeredWindowAttributes and testing the result for NULL. But you can't make transparency effects similar to what the layering can offer on Windows 95/98.
-Antti Keskinen
----------------------------------------------
The definition of impossible is strictly dependant
on what we think is possible.
|
|
|
|
|
Hi Antti Keskinen,
Thanks a lot.
Xiaobin
|
|
|
|
|
It's impossible.hahahahahah.....
windows98 is rubbish.Bless u.
|
|
|
|
|
Try to paint the window with a brush having a brush style BS_HOLLOW
use log brush for this.
|
|
|
|
|
Hi,
Details:
created Win32 console application
includes - process.h windows.h, etc
using _beginthread
Problem:
the following error occurs
error C2065: '_beginthread' : undeclared identifier
How do I link with one of the multithreaded C run-time libraries
& which one should I use?
Caoimh
|
|
|
|
|
You'll need pass /MT to the command line.
In VS.NET:
Right-click on your Project in the Solution Explorer and click on Properties, C/C++ -> Code Generation.
Rickard Andersson
Here is my card, contact me later!
UIN: 50302279
Sonork: 37318
|
|
|
|
|
Thank You. Works perfectly as you would expect
Caoimh
|
|
|
|
|
Check CreateThread
and link with kernel32.lib
Papa
while (TRUE)
Papa.WillLove ( Bebe ) ;
|
|
|
|
|
CreateThread should largely be avoided on the desktop, because it doesn't allow the C/C++ run-time libraries to set themselves up for the new thread correctly. Better to use _beginthreadex and one of the the multi-threaded CRT versions.
Note that the single-threaded versions of the CRT aren't thread-safe anyway; you can do your program a fair amount of damage if you try to use the single-threaded version from multiple threads.
On Windows CE devices, use CreateThread, because the system entry points and the C run-time are all in coredll.dll - the system is C run-time aware. You can't use _beginthread or _beginthreadex anyway, because they're not there.
|
|
|
|
|
hi,
i have a dialog based application in which i am loading images and editing it..for this i need the undo and the redo functions ... any idea how do i go about it.
Any help is warmly welcomed.
Thanking you.
Satadru.
|
|
|
|
|
|
|
While both of your replies contained the right text, the underlying links were wrong. Did you try them out?
Five birds are sitting on a fence.
Three of them decide to fly off.
How many are left?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
