 |
|
|
|
Topic: Windows XP problem.
|
| By: Pablo | Posted on: May 9 2013 at 07:10:11 AM | Hi, I have a Visual Basic application which uses SComm32 and works fine with Windows 7. However, with Windows XP the application doesn't start. I am using a manifest file and a Windows API call to InitCommonControls in order to give an XP look to my application. If I remove the manifest file from the applications path the application starts correctly (but no XP look, of course). If I keep the manifest file and remove the Scomm32 component from the application, it also starts correctly so the problem is the combination of both (manifest file and SComm32 component).
Can you help me ?
Thanks, | |
| By: Guest | Posted on: May 9 2013 at 07:59:23 AM | Let me see if i understand this correctly.
You use the api call to give your application an 'XP' look which, i assume, is what you want when using windows 7. I can understand that you want you application to have a common look under all versions of windows.
But if the same call is made when actually running in XP the the application doesnt start.
Is there any error message ?
Although, why can't you just check to see which version of windows is running and when running under XP just dont make the api call. | |
| By: Pablo | Posted on: May 9 2013 at 08:25:58 AM | There isn't any error message.
I must make the API call also when running under XP because otherwise the application doesn't look like XP. This is a widely known problem with Visual Basic 6: some components (buttons, checkboxes...) look like older Windows versions. They look "squared" instead of rounded.
Anyway, I have just solved the problem. I don't know whay but the fact is that I only get the error when I insert the MSComm32 object on an MDI form. I removed it from there and inserted into a SDI form and the problem was solved.
Thanks, | |
|
