G
Guest
Hello
Some years ago I wrote an application (a sequencer) in VB5 and then in VB6 which records and plays MIDI signals from and to an electronic organ. The MIDI information is displayed in a RichText box (named Data, say). While playing, the info about the particular MIDI signal being sent is coloured red (and once again black after sending) simultaneously, using the statement
Data.SelStart=<location in the string
Data.SelLength=<length of the info
Data.SelColor=<red or black
Now the program has been upgraded to VB.NET and the ActiveX RichTextBox control has been replaced by the equivalent System.Windows.Forms control. It appears that the execution time for the above three statements is about 30 to 50 times longer than in case of the AxRTBox control. Hence the info shown is lagging increasingly behind the sent data. The time lag is dependent on the number of characters in the RT Box; longer text yield longer execution times. This is not the case with AxRTBoxes; they show constant times. Hence I am back to AxRTBoxes, but that is rather disappointing as they will be phased out in due course
Anyone who knows this problem? Would it be a real bug, to be fixed by Microsoft
Thank you
Reinier
Some years ago I wrote an application (a sequencer) in VB5 and then in VB6 which records and plays MIDI signals from and to an electronic organ. The MIDI information is displayed in a RichText box (named Data, say). While playing, the info about the particular MIDI signal being sent is coloured red (and once again black after sending) simultaneously, using the statement
Data.SelStart=<location in the string
Data.SelLength=<length of the info
Data.SelColor=<red or black
Now the program has been upgraded to VB.NET and the ActiveX RichTextBox control has been replaced by the equivalent System.Windows.Forms control. It appears that the execution time for the above three statements is about 30 to 50 times longer than in case of the AxRTBox control. Hence the info shown is lagging increasingly behind the sent data. The time lag is dependent on the number of characters in the RT Box; longer text yield longer execution times. This is not the case with AxRTBoxes; they show constant times. Hence I am back to AxRTBoxes, but that is rather disappointing as they will be phased out in due course
Anyone who knows this problem? Would it be a real bug, to be fixed by Microsoft
Thank you
Reinier