quote:
Originally posted by Shunter
Yeah, i read a lot about your program and i decided that i'll try .NET instead of APIs...
If you can program in VB.NET, using it would be easier for you than using VB 6, I think. I wrote the translator in VB.NET because I can't program in .NET and because when I did the first release I hadn't got it yet
quote:
Originally posted by Shunter
quote:
Originally posted by Choli
Text1.SelStart = 2
Text1.SelLength = 2
Text1.SetFocus
I'm like and ... i spent 2 hours looking for such an expression in MSDN library, with no result... that's when i decided to use .NET. I believed SetFocus is only useful to give a control focus, and the library did not mention that it had a very useful another use...
But at least i'm slightly experienced in .NET now, too
the .SetFocus is there to give the textbox the focus so you can see what's selected, because when you create a textbox it has its HideSelection property set to true.
If when you create the textbox you set the HideSelection property to false, you don't need the .SetFocus line
quote:
quote:
Originally posted by Patchou
Quick note about VB: Visual Basic works entirely in Unicode internally.
... however with common expressions or using FSO it does not like opening unicode files. there is a ANSI->Unicode conversion function StrConv, and with it i could kick it to life, but the scrolling problem still remained.
Now i see that it was not VB6 that lacked ability, but me
I'll try and make some filters to add some intelligence to the app.
Thanks for all the help!
FSO=FileSystemObject? I've never used that and don't know what's that
and yes, when you open a file, VB reads ansi strings, however it stores them as unicode strings. That may be a big problem with some files if you open them with the open function. You can work arround that by using APIs.
btw, what has the scrolling thingy to do with ansi/unicode? I don't see any problem with scrolling.