|
Hi
I have a VB6 ActiveX that displays a form with some controls: text box, buttons, radio buttons, Sheridan date control.
I call this form from a C# Windows form. This is done by a) adding a reference to the COM object b) instantiating the object c) Calling a method that displays the form.
The problem is that when the form is displayed, the controls style changes:
a) The text box becomes flat (not 3D)
b) The command button edges are rounded
c) The date control shows squares and funny shapes instead of numbers
d) The raduo buttons, that are located inside a frame, are black.
a and b are no big deal, c & d are obviously serious problem.
If I display the form from a C# console application then there is no problem: the controls look exactly as they do in the VB design. Also, if I compile the form to an EXE and call the EXE from a C# windows form, there is no problem.
It wasn't always like that: this problem started only recently, possibly as a result of Windows update, service pack... I am not sure what.
Does anyone know of a way to fix that, or some Windows settings to fix the problem?
|
|
|
|
|
Did you enable Visual Styles in your C# app?? Just a guess, but it's the only other thing I can think of that would change.
If you suspect it's a service pack or patch, build a test machine to verify this, without the suspected patches and service packs. THen add each one until the problem shows up.
|
|
|
|
|
Thanks for that Dave.
I didn't enable Visual Styles.
I did find that if I go to My Computer | Properties | Advanced | Performance | Visual effects , and turn off "Use visual styles on windows and buttons", then it solves the problem with most of the controls I mentiod - text boxes, buttons, radio buttons. The only control I have a problem with now is the Sherida Calander control. I will look for a solution for this one now.
|
|
|
|
|
Replacing the Sheridan date control (SSCalendarWidgets_A.SSDateCombo) with the Microsoft Date Picker (MSComCtl2.DTPicker) solves the problem. But now I noticed there is a similar problem with the Sheridan grid: when a line is edited, the content of the field in focus is garbage 
|
|
|
|
|
Hello Guys!!!
I m doing a program base on AxMSChart now i m working on that. Here a problem arrived
When the row count is increase high then it is start flickering why it is happening some give me solution.
Now i m assigned it
AxMSChart.Rowcount=5000
Ananda.
|
|
|
|
|
non-bugging Errors wrote: When the row count is increase high then it is start flickering why it is happening
It happens because you're adding too much information to the chart control, probably more than what's needed to render the graph, and it's spending most of it's time processing and drawing all that data instead of showing the final graph image on the screen.
If you're using VB.NET, I highly suggest using a third party charting library, like ZedGraph[^].
|
|
|
|
|
or if using 3rd party tools is out of hand try ControlStyles.DoubleBuffer property. It should reduce the flickering.
|
|
|
|
|
Hi, I am in need of help, I am new to VB and crystal reports. I am having trouble with images on the report. For some reason, the image is blurry. I store the file path in sql2000 db and the image on the dev machine. I am retrieving and saving the image correctly (clear image) onto my local machine (this is a temporary path), but for some reason, the report displays the image blurry. I even tried to insert a fixed picture (which is also clear) but still get the same problem. So I am assuming, there's a problem with the way crystal reports is pulling in the image. Any ideas on how to fix this?
Any help is most appreciated.
Thanks
|
|
|
|
|
I have no idea how to fix it since I don't use Crystal Reports, but the problem is because the image is being scaled when displayed and CR is doing a bad job of it. Also, is your report picture larger than the size of the original image??
|
|
|
|
|
Hi,
I have to create a method which will be called for 5400 times roghly which creates a directory and put the data of the user in it.
For performance wise which one is good either
1. MkDir Left$(strPathName, lngPos)
2. Windows API or 3. FSO. which one gives more performance.
Whats the DLL to be included for Windows API?
Thanks,
Aleem Mohammad.
Thanks & Regards,
Md. Abdul Aleem
NIIT technologies
modified on Thursday, November 13, 2008 3:08 AM
|
|
|
|
|
|
Hi,
Can u please tell me which dll file should be enclosed to write this method or in which class "CreateDirectory()" function exists.
If possible some small code snippet.
Thanks,
Aleem Mohammad.
Thanks & Regards,
Md. Abdul Aleem
NIIT technologies
modified on Thursday, November 13, 2008 5:05 AM
|
|
|
|
|
|
Hi,
I am able to work it out with FileSystemObject as below but the same code I want to write with Windows API, can anybody please help me in sorting out this problem.
Dim fso As New FileSystemObject
Dim fold1 As Folder
If Not (fso.FolderExists("C:\Fold1")) Then
fold1 = fso.CreateFolder("C:\Fold1")
End If
Thanks,
Aleem Mohammad.
Thanks & Regards,
Md. Abdul Aleem
NIIT technologies
|
|
|
|
|
From the cycle "writing your code in 24 hours from scratches". Seriously take the time and read a few resources yourself rather than asking everything on forums. Not to mention the fact that if you dun really understand what's going on in the copied code you will be unable to debug it if something occurs. Then probably we'll get a new round of "questions".
|
|
|
|
|
Sorry friend it is completed but still I tried as a human I have to ask to others. Sorry if am disturbing u.
And thanks a lot for the help u all have given me.
Thanks a Lot,
Aleem Mohammad.
Thanks & Regards,
Md. Abdul Aleem
NIIT technologies
|
|
|
|
|
You're not disturbing us. We're just pointing out that your overcomplicating your code and your going to run into too many walls that you don't need to run into.
|
|
|
|
|
Never Add dlls when you can use it from the namespace
|
|
|
|
|
Hi,
yes I havent added any dll but I was confusing. Thanks a lot friend.
Aleem Mohammad
Thanks & Regards,
Md. Abdul Aleem
NIIT technologies
|
|
|
|
|
You don't need the Windows API to do this. It's not going to give you a performance benefit. You're creating a directory on a drive, not calculating PI to 1,000,000 digits.
Keep your code simple and easy to maintain. Use the FileSystemObject to do this. If you do this with the Windows API, you're going to get lost, very, VERY quickly and write about 50 times the code you need to write to do this little job.
|
|
|
|
|
i have 2 textboxes and each of the textbox is running on different thread. If i wan to display the value which is on the txtbox1 to txtbox2 i have a error can cross-thread operation not valid. What should i do to solve tis problem?
|
|
|
|
|
try this
use files to trasfer data between your textboxes.
write content of textbox1 text to a temporary file, read it from second thread and put it in the second textbox2.
Rajesh B --> A Poor Workman Blames His Tools <--
|
|
|
|
|
Maybe using a delegate ...
|
|
|
|
|
|
Dave Kreskowiak wrote: 
Yep. Almost made me gag on my coffee reading the suggestion of using files 
"The clue train passed his station without stopping." - John Simmons / outlaw programmer
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
"Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
