|
hmm I thought one wasn't supposed to call any ole init funcs from dllmain.
Maybe this is irrelevant, but from the docs:
"Because there is no way to control the order in which in-process servers
are loaded or unloaded, do not call CoInitialize, CoInitializeEx, or
CoUninitialize from the DllMain function."
What thread is DllMain called on? Does it even make sense there? I dunno...
my brain is fried today (death in family...nightmare week).
Mark
Mark Salsbery
Microsoft MVP - Visual C++
![Java | [Coffee]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/coffee.gif)
|
|
|
|
|
in-process servers, hmm, I would like to see more of that. Do you have a link? I was not thinking about COM servers but just DLL's as it has been many years since I have developed any COM servers. I guess my recent experience has limited my thinking *that's weak*. In the recent past my DLL models have been for libraries that use COM servers rather than implementing them. I have never had a problem even though multiple init's are surely happening within the process.
Mark Salsbery wrote: What thread is DllMain called on?
The current process is creating a new thread. When this occurs, the system calls the entry-point function of all DLLs currently attached to the process. The call is made in the context of the new thread.
link[^]
led mike
|
|
|
|
|
led mike wrote: I would like to see more of that. Do you have a link?
CoInitializeEx()[^] - Remarks, last line.
That's why I said it might be irrelevant to this case....maybe that just applies to COM servers.
Thanks for the link about the DllMain thread! I was just reading that 
Mark
*EDIT* OOps - fixed the post LOL
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
I did follow the code into AfxOleInit(), & since it's in the context of a DLL, it just sets a variable to -1 & returns TRUE w/out really doing anything. It assumes calling process as initialized OLE.
|
|
|
|
|
Cool. Thanks for the update!
Mark
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
Hi i had posted this before too i have and image acquisition code that acquires image from CCD camera and stores it to pointer named "*memory"
pl_exp_start_seq(hCam, memory)
i want to display this memory as bmp file and save it to my hard disk, i did write code for it but that saves it in 8 bit format and i loose a lot of valuable information can any one please help, y code is as follows and thankz in advance
void Create_DIB( HWND hWnd )
{
HDC hDC;
unsigned char i;
long k,j, NumBytes;
LPBITMAPINFO info;
unsigned char *dat;
DWORD error;
hDC = GetDC (hWnd) ;
// Intialize BITMAPINFOHEADER data.
//.................................
bi.biSize = sizeof (BITMAPINFOHEADER) ;
bi.biWidth = W;
bi.biHeight = -H; // top-down DIB
bi.biPlanes = 1;
bi.biBitCount = COLORBITS;
bi.biCompression = BI_RGB;
bi.biSizeImage = ( ALIGNLONG( (W * COLORBITS)/8 ) * H);
bi.biXPelsPerMeter = 0;
bi.biYPelsPerMeter = 0;
bi.biClrUsed = 256;
bi.biClrImportant = 256;
// Allocate memory for BITMAPINFO structure.
//..........................................
NumBytes = sizeof(BITMAPINFOHEADER) + 256 * sizeof (RGBQUAD); // +
//( ALIGNLONG( ( W * COLORBITS ) / 8 ) * H );
lpbi = (BITMAPINFOHEADER*)GlobalAlloc( GPTR, NumBytes );
if( lpbi == NULL )
{
LPVOID lpMsgBuf;
FormatMessage( FORMAT_MESSAGE_ALLOCATE_BUFFER |
FORMAT_MESSAGE_FROM_SYSTEM |
FORMAT_MESSAGE_IGNORE_INSERTS,
NULL, GetLastError(),
MAKELANGID(LANG_NEUTRAL, SUBLANG_DEFAULT), // Default language
(LPTSTR) &lpMsgBuf, 0, NULL );
// Display the string.
MessageBox( NULL, (LPCTSTR)lpMsgBuf, "Error", MB_OK | MB_ICONINFORMATION );
// Free the buffer.
LocalFree( lpMsgBuf );
exit( EXIT_FAILURE ); // Get out now!
}
// Copy BITMAPINFOHEADER information.
//...................................
*lpbi = bi;
// Create The Palette
info = (LPBITMAPINFO) lpbi;
for ( i=0; i<255; i++ )
{
info->bmiColors[i].rgbRed = i;
info->bmiColors[i].rgbBlue = i;
info->bmiColors[i].rgbGreen = i;
info->bmiColors[i].rgbReserved = 0;
}
// Set pointer to bitmap’s bit data.
//..................................
// lpstBitmap = (LPSTR)lpbi + (WORD)sizeof(BITMAPINFOHEADER) +
// (256 * sizeof(RGBQUAD));
hBitmap = ::CreateDIBSection(hDC,(LPBITMAPINFO)lpbi, DIB_RGB_COLORS,(VOID **)&lpstBitmap, NULL,0);
dat = (unsigned char*)lpstBitmap;
for ( k=0; k< H; k++ )
for ( j = 0; j < W; j++ )
*dat++ = (unsigned char)k;
// Create uninitialized DIB bitmap.
//.................................
/* hBitmap = CreateDIBitmap( hDC,
&bi,
0 ,
0,
(LPBITMAPINFO) lpbi, */
error = GetLastError();
ReleaseDC( hWnd, hDC);
}
void Save(int num)
{
CString prefix = "C:\\Documents and Settings\\Garner Lab\\My Documents\\Xanoscopeimages\\image";
char buf[4];
itoa(num, buf, 10);
CString number = buf;
CString suffix = ".bmp";
fullname = prefix + number + suffix;
CImage image;
image.Attach(hBitmap);
image.Save(fullname); // save as BMP
image.Detach();
|
|
|
|
|
Since you're using CImage, you can simplify this and let the CImage class do the work.
Create a CImage object and use its Create() or CreateEx() methods to
create the DIB section. Then you can use the GetBits() and GetPitch()
methods to copy your pixel data into the DIB section.
Review the BITMAPINFOHEADER documentation (see biBitCount) for 16-bit support
in DIBs. Note 16-bit grayscale is not supported.
24 bit DIBs are straight-forward.
Mark
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
Mark
hey thnkz a ton Mark for the help but i had one more query if you could help i m trying to save an image from CCD camera dats sending data as pointer now is there a way i can convert this image data into TIFF fileand save it on disk , as TIFF supports 12bit to my knowledge if yes where can i look for help or could you help me with it, as currently i m converting it to bitmap and dats where i m lossing all my information in terms of resolution.
Dipen
|
|
|
|
|
GDI+[^] supports loading/saving TIFF files but doesn't support 12-bit images.
16-bit color and grayscale images are supported, so you could upsample the
image data to 16bpp.
The most difficult option for working with TIFF files would be to write your own
loader/saver using the TIFF Specification[^]
An easier method would be to use a third party library, like LibTIFF[^]
Mark
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
I have a legacy VC++ 6.0 program that is quite large. Every dialog is user created, even though for many of the dialogs, there was a template created in the resources for the dialog. The problem I am having is that when I call a dialog that allows the user to input an ID number and a PIN to log on to this application, the first time the 'keypad' is displayed, it is displayed in the context of the template that was created, but the second time it is called, the 'keypad' is displayed in the 'user defined' context. Is there a way to get around this problem? It has been baffling me now for months, and granted, I am not a VC++ power user by any means.
Thanks for your assistance.
John P.
|
|
|
|
|
What happens if you remove the template dialog?
"Normal is getting dressed in clothes that you buy for work and driving through traffic in a car that you are still paying for, in order to get to the job you need to pay for the clothes and the car and the house you leave vacant all day so you can afford to live in it." - Ellen Goodman
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
|
|
|
|
|
If I remove the template, then I get nothing when I call the keypad class.
The operation of this application is quite large. I'm not sure if you have some idea of what an "Instructor Operating System (IOS)" is to a flight simulator, but it controls every aspect of the flight simulator as far as settings go. In order to use this system, it was decided that it should be user and password protected, so that not just anyone could enter the cockpit and use the simulator. Before I added the password protection modules, the keypad came up as it was designed (being the user design and not just the template). The user design uses some of the template and adds on to it's functionality. It would take paragraphs to fully explain the inner workings of this application, so I'm not sure that you might be able to come up with a viable suggestion as to how to make this work correctly.
I was wondering if it was possible to 'create' the keypad at some other location that's not visible, and then delete it, so that when I call it again, it will not be the first time it has been called and created??
John P.
|
|
|
|
|
Are you using MFC?
"Normal is getting dressed in clothes that you buy for work and driving through traffic in a car that you are still paying for, in order to get to the job you need to pay for the clothes and the car and the house you leave vacant all day so you can afford to live in it." - Ellen Goodman
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
|
|
|
|
|
|
Ok, so how are you instantiating and creating the "login" dialog?
"Normal is getting dressed in clothes that you buy for work and driving through traffic in a car that you are still paying for, in order to get to the job you need to pay for the clothes and the car and the house you leave vacant all day so you can afford to live in it." - Ellen Goodman
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
|
|
|
|
|
I create an instantiation of CLogin clog. This creates the login dialog which has text boxes for holding the UserID and PIN values. There are buttons to select the entry for the UserId and PIN and this in turn calls the Keypad dialog. When the user enters the UserID and PIN numbers, they are placed in the text boxes (one at a time).
John P.
|
|
|
|
|
jparken wrote: I create an instantiation of CLogin clog.
Do you then call Create(), CreateIndirect(), or InitModalIndirect()?
"Normal is getting dressed in clothes that you buy for work and driving through traffic in a car that you are still paying for, in order to get to the job you need to pay for the clothes and the car and the house you leave vacant all day so you can afford to live in it." - Ellen Goodman
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
|
|
|
|
|
I don't call any of these, David. And none of these are called for Keypad as well.
John P.
|
|
|
|
|
I guess I've failed to understand the problem. What is meant by "user design?"
"Normal is getting dressed in clothes that you buy for work and driving through traffic in a car that you are still paying for, in order to get to the job you need to pay for the clothes and the car and the house you leave vacant all day so you can afford to live in it." - Ellen Goodman
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
|
|
|
|
|
I guess that was a poor choice of wording on my part. Almost all the dialogs have been created from a template. So I guess the proper terminology would be "owner drawn".
John P.
|
|
|
|
|
Ok, so what is an "owner drawn" dialog, and how does it differ from a non-owner drawn dialog?
"Normal is getting dressed in clothes that you buy for work and driving through traffic in a car that you are still paying for, in order to get to the job you need to pay for the clothes and the car and the house you leave vacant all day so you can afford to live in it." - Ellen Goodman
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
|
|
|
|
|
In order to explain that, I would have to enter the code for the module that from which just about all the other dialogs are derived. That would be a couple of pages of code that I doubt anyone would want me to paste on the Forum. Here's just a small example of what I'm referring to:
<br />
const UINT CIosDialog::BTN_ID[CIosDialog::NUM_BUTTONS] =<br />
{<br />
IDC_BN_0, IDC_BN_1, IDC_BN_2, IDC_BN_3, IDC_BN_4, <br />
IDC_BN_5, IDC_BN_6, IDC_BN_7, IDC_BN_8, IDC_BN_9, <br />
IDC_BN_10, IDC_BN_11, IDC_BN_12, IDC_BN_13, IDC_BN_14, <br />
IDC_BN_15, IDC_BN_16, IDC_BN_17, IDC_BN_18, IDC_BN_19, <br />
IDC_BN_20, IDC_BN_21, IDC_BN_22, IDC_BN_23, IDC_BN_24, <br />
IDC_BN_25, IDC_BN_26, IDC_BN_27, IDC_BN_28, IDC_BN_29,<br />
IDC_BN_30, IDC_BN_31, IDC_BN_32, IDC_BN_33, IDC_BN_34, <br />
IDC_BN_35, IDC_BN_36, IDC_BN_37, IDC_BN_38, IDC_BN_39,<br />
IDC_BN_40, IDC_BN_41, IDC_BN_42, IDC_BN_43, IDC_BN_44, <br />
IDC_BN_45, IDC_BN_46, IDC_BN_47, IDC_BN_48, IDC_BN_49, <br />
IDC_BN_50, IDC_BN_51, IDC_BN_52, IDC_BN_53, IDC_BN_54, <br />
IDC_BN_55, IDC_BN_56, IDC_BN_57, IDC_BN_58, IDC_BN_59, <br />
IDC_BN_60, IDC_BN_61, IDC_BN_62, IDC_BN_63, IDC_BN_64, <br />
IDC_BN_65, IDC_BN_66, IDC_BN_67, IDC_BN_68, IDC_BN_69<br />
};
The same is done for labels, text ids, etc.
Then for example in another file:
CEnvironmentControl::BTN_INFO_STRUCT CEnvironmentControl::btnInfo[] =<br />
{<br />
{true, IDB_BLUE_BTN_WIDE_OFF, IDB_BLUE_BTN_WIDE_ON, <br />
"B A R O P R E S S U R E\n-->\n", BaroPressure, CStringType, <br />
&baroPressureString,NULL,"", 0},<br />
<br />
{true, IDB_BLUE_BTN_WIDE_OFF, IDB_BLUE_BTN_WIDE_ON, <br />
"A I R P O R T T E M P\n-->\n", AirportTemp, FloatType, <br />
&trainerData.envInfo.CURRENT_AIRPORT_TEMP, NULL, " \272 C", 0}, <br />
<br />
{true, IDB_BLUE_BTN_WIDE_OFF, IDB_BLUE_BTN_WIDE_ON, <br />
"S U R F A C E W I N D S\n-->\n", SurfaceWinds, CStringType, <br />
&envData.surfaceWindsString, NULL, "", 0},<br />
<br />
{true, IDB_BLUE_BTN_WIDE_OFF, IDB_BLUE_BTN_WIDE_ON, <br />
"A L O F T W I N D S\n( 8000' MIN ALTITUDE )\n-->\n", AloftWinds, CStringType, <br />
&envData.aloftWindsString, NULL, "", 0},<br />
<br />
{true, IDB_BLUE_BTN_WIDE_OFF, IDB_BLUE_BTN_WIDE_ON, <br />
"W I N D G U S T S\n-->\n", WindGusts, FloatType, <br />
&envData.info.GUSTS, NULL, " kts", 0},<br />
<br />
{true, IDB_BLUE_BTN_WIDE_OFF, IDB_BLUE_BTN_WIDE_ON, <br />
"T U R B U L E N C E\n-->\n", Turbulence, IntegerType, <br />
&envData.info.TURBULENCE, NULL, "", 0},<br />
.<br />
.<br />
.<br />
<br />
Hope this helps explain it a little more. I know it's confusing. I originally, and still do, feel somewhat overwhelmed by this application.
John P.
|
|
|
|
|
So are these controls added to the dialog in OnInitDialog() or some other initialization function? The problem, then, is that they do not show up the first time the dialog is rendered but do show up each time thereafter. Is that correct?
"Normal is getting dressed in clothes that you buy for work and driving through traffic in a car that you are still paying for, in order to get to the job you need to pay for the clothes and the car and the house you leave vacant all day so you can afford to live in it." - Ellen Goodman
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
|
|
|
|
|
<br />
class CKeypad : public CDialog<br />
{<br />
public:<br />
CKeypad(CWnd* pParent, const WinInfoStruct); <br />
~CKeypad();<br />
<br />
bool Get_Integer(CString Label, int Min, int Max, int *result=0);<br />
bool Get_Float(CString Label, float Min, float Max, float *result=0);<br />
bool Get_Latitude(CString Label, LAT_DEGREES *result=0);<br />
bool Get_Longitude(CString Label, LON_DEGREES *result=0);<br />
bool Get_Angle(CString Label, DEGREES *result=0);<br />
bool Get_Day(CString Label, int Min, int Max, int *result=0);<br />
bool Get_Month(CString Label, int Min, int Max, int *result=0);<br />
bool Get_Time (CString Label, TimeFormats Format, SECONDS Min,<br />
SECONDS Max, SECONDS *result=0);<br />
bool Get_BaroPress (CString Label, float Min, float Max, float *result=0);<br />
enum { IDD = IDD_KEYPAD };<br />
<br />
private:
<br />
enum CONSTANTS { NUM_BUTTONS = 14 };<br />
<br />
WinInfoStruct winInfo;<br />
CSuperFrame superFrame;<br />
CSuperButton m_EntryBtn[NUM_BUTTONS];<br />
CSuperButton m_Backspace;<br />
CSuperButton m_Enter;<br />
CSuperButton m_Cancel;<br />
CSuperButton m_sbNorth;<br />
CSuperButton m_sbSouth;<br />
CSuperButton m_sbEast;<br />
CSuperButton m_sbWest;<br />
CEntryBuffer m_EntryBuffer;<br />
CString m_Title;<br />
CString m_ErrorBuffer;<br />
bool settingLat;<br />
bool m_bShowDirections;<br />
CRect titleRect;<br />
<br />
const static UINT btnId[NUM_BUTTONS];<br />
<br />
private:
<br />
void ProcessCharacter(char C);<br />
void UpdateDisplay(bool New_Title);<br />
<br />
<br />
protected:<br />
virtual void DoDataExchange(CDataExchange* pDX);
<br />
protected:<br />
afx_msg void OnBn1();<br />
afx_msg void OnBn2();<br />
afx_msg void OnBn3();<br />
afx_msg void OnBn4();<br />
afx_msg void OnBn5();<br />
afx_msg void OnBn6();<br />
afx_msg void OnBn7();<br />
afx_msg void OnBn8();<br />
afx_msg void OnBn9();<br />
afx_msg void OnBn0();<br />
afx_msg void OnBn00();<br />
afx_msg void OnBn000();<br />
afx_msg void OnBnDec();<br />
afx_msg void OnBnNeg();<br />
afx_msg void OnBnEnter();<br />
afx_msg void OnBnBs();<br />
afx_msg void OnBnEast();<br />
afx_msg void OnBnNorth();<br />
afx_msg void OnBnSouth();<br />
afx_msg void OnBnWest();<br />
virtual BOOL OnInitDialog();<br />
afx_msg HBRUSH OnCtlColor(CDC* pDC, CWnd* pWnd, UINT nCtlColor);<br />
afx_msg void OnPaint();<br />
virtual void OnCancel();<br />
DECLARE_MESSAGE_MAP()<br />
};<br />
<br />
<br />
#pragma pack(pop)<br />
<br />
#endif // !defined(AFX_KEYPAD_H__A3105D12_254A_11D2_804C_00104B2D1F4C__INCLUDED_)<br />
I use the GetInteger() function to get the UserID and PIN numbers.
John P.
|
|
|
|
|
So what was the previous mention of CLogin for? Is that somehow related to CKeypad?
"Normal is getting dressed in clothes that you buy for work and driving through traffic in a car that you are still paying for, in order to get to the job you need to pay for the clothes and the car and the house you leave vacant all day so you can afford to live in it." - Ellen Goodman
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
