|
Thanks for the reply,
I've tried according to you but the problem has not been solved.
I've added a new dialogbox and a class that implements it and when I use
the code as below when a button of the toolbar is clicked.
CDlg2 ob;
ob.DoModal();
The dialogbox doesn't appear.
So what is the problem with the resource file that I am not getting.
ritz1234
|
|
|
|
|
ritz1234 wrote: When I click on the third tab I hide all the controls except the
newly added lablel and textbox for this third tab of the dialogbox.
But I can't see them.
Have you used the debugger to find out why?
"Love people and use things, not love things and use people." - Unknown
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
|
|
|
|
|
Thanks for the reply David.
The toolbar is a ATL COM DLL how can I debug it?
I badly need to solve this problem?
ritz1234
|
|
|
|
|
ritz1234 wrote: The toolbar is a ATL COM DLL how can I debug it?
The same way you would any other application. Compile in debug mode. Set a breakpoint using F9. Start with F5. Step using F10 and F11.
"Love people and use things, not love things and use people." - Unknown
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
|
|
|
|
|
Although the breakpoint has not reached.
it gives me the debug assertion failure of when I call DoModal() to show
the dialogbox just added in resource file.
Progame:IEXPLORE.EXE
File:afxwin1.inl
line:22
ritz1234
|
|
|
|
|
ritz1234 wrote: File:afxwin1.inl
line:22
Have you looked at this line?
"Love people and use things, not love things and use people." - Unknown
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
|
|
|
|
|
The content of this file is as below
{ ASSERT(afxCurrentResourceHandle != NULL);
ritz1234
|
|
|
|
|
Has the ActiveX control been registered? Have you tried removing any newly-added code until the problem goes away?
"Love people and use things, not love things and use people." - Unknown
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
|
|
|
|
|
yes,the COM DLL has been registered.
If possible reply soon.
ritz1234
|
|
|
|
|
I am having a bit of an odd problem that I can't figure out.
I am designing a dialog with a width of 500 pixels.
My screen resolution width is 1680.
So, logically, I would assume that the dialog would take up under one third of the window width.
However, the dialog actually takes up half. I don't suppose anyone has any idea why this is.
The only thing I can think of was something similar back in my beginning days of Windows programming with VB 4.0 and the GUI designer used to use something called "twips" (or something) for measurements. Is the problem I'm having similar, or does VS have some sort of scaling setting I'm not aware of?
Thanks
|
|
|
|
|
have you changed the dialog font?? from properties.
|
|
|
|
|
Why would I change the font? Does the dialog size scale based on the font size selected?
|
|
|
|
|
yes i had faced similar problem when i increased the dialog font size from properties.
|
|
|
|
|
and BTW the 500 width you saw was it in Resource editor??
If yes i dont think it is in pixels like your screen resolution.
Do GetWindowRect() to get the dialog width in pixels.
|
|
|
|
|
I see. I assume there is no way to diable this feature?
If not, I'll have to code the dialog manually (which I'd rather not do).
Changing the font is not really an option as it would have to be changed in a large number of places, for consistency. Something I don't have time for.
Is this problem a VS resource editor problem (feature?), or an issue with dialogs in Windows itself?
|
|
|
|
|
Brian Dunne wrote: I am designing a dialog with a width of 500 pixels.
Dialog's are measured in DLUs.
Brian Dunne wrote: My screen resolution width is 1680.
Screen resolution is measured in pixels. It's really a bad idea to design dialogs in terms of pixels. Screen resolution will vary from machine to machine, and any attempt to think about pixels at design time is doomed to failure. Don't even worry about it. If you need something sized in pixels to a specific size, you have to do it at runtime.
"Love people and use things, not love things and use people." - Unknown
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
|
|
|
|
|
typedef UINT (CALLBACK* LPFNDLLFUNC1)(DWORD,UINT);
...
LPFNDLLFUNC1 lpfnDllFunc1; // Function pointer
The above declaration seems confusing and any easy way to declare func. ptrs.
|
|
|
|
|
I thought typedef is supposed to be easy way to declare function ptrs.  
|
|
|
|
|
LPFNDLLFUNC1 lpfnDllFunc1;
is alternative to
UINT (CALLBACK* lpfnDllFunc1)(DWORD,UINT);
Which one does look simpler?
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
|
|
|
|
|
I think maybe he was looking for something simpler, like:
typedef UINT (CALLBACK* X)(DWORD,UINT);
...
X y;
"Love people and use things, not love things and use people." - Unknown
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
|
|
|
|
|
or something more managed, like
delegate int X (int, int);
...
X x;
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
|
|
|
|
|
Hi,
How can I maximize the dialog box?
|
|
|
|
|
call ShowWindow(SW_MAXIMIZED)
|
|
|
|
|
The final D is a common mistake (I did it often).
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
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
