tag:blogger.com,1999:blog-19326029.post6145806697392482595..comments2024-03-22T14:31:14.815+01:00Comments on GFA-BASIC 32 for Windows: The Collection Ocx (part 2)Sjouke Hamstrahttp://www.blogger.com/profile/17490567785357245752noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-19326029.post-33927350585002968542009-10-01T11:19:07.859+02:002009-10-01T11:19:07.859+02:00I allready understand the API-Functions, but i thi...I allready understand the API-Functions, but i think, just a idea, that the possibility must be given to manage that with GetA or GetW and same with PutA and PutW. <br />If someone have an idea how to manage the problem, off course he must not do that just for fun, i will pay for his work and his time.<br />Therefore please read my posting from 22.09.2009 If you have a idea, let me know how i can contact you.Michael Farnbauerhttp://www.gmx.denoreply@blogger.comtag:blogger.com,1999:blog-19326029.post-47897907898157528432009-09-25T10:40:29.884+02:002009-09-25T10:40:29.884+02:00There is an increasingly amount of questions on su...There is an increasingly amount of questions on support of UNICODE controls. One of these days I will get into that. First let me describe what is happening in the background.<br /><br />Whenever you use an Ocx command, GFA-BASIC 32 creates the ANSI version of the control. Then the properties and methods take UNICODE strings (COM derictive) as a parameter. Before passing the UNICODE string GFA-BASIC converts the ANSI string datatype to UNICODE to pass it on to the runtime DLL. Then the runtime function convert the string back to ANSI to call the Windows API function for that particular property or method. Than, o irony, Windows converts it back to UNICODE ...<br /><br />To allow the user to enter UNICODE text, all you need to do is to create a the wide-variant of the control, rather than the ANSI version. Than, automatically, Windows accept UNICODE characters. What we need to do is to get the UNICODE out of the control. This can be done the API way ofcourse. For the moment I suggest, you use UNICODE on your own, without the properties and methods that make the Ocx controls so easy to use.<br /><br />To get advantage from the Ocx events you can wrap the control into a COM interface using the WrapXXX commands. You can use the event subs, but not the properties and methods that take a string data type. Most other properties taking a Bool or Integer may still work. Just test!Sjouke Hamstrahttps://www.blogger.com/profile/17490567785357245752noreply@blogger.comtag:blogger.com,1999:blog-19326029.post-49957288573549196102009-09-22T15:12:39.621+02:002009-09-22T15:12:39.621+02:00if you enter in a textbox for example Chinese the ...if you enter in a textbox for example Chinese the text string returns only ASCII code, no UNICODE and the textbox shows only trash. If I received a pure UNICODE, which means two byte per character, I would be able to fill an IBL-OCX or a list box.<br /><br />But all OCX elements only understand ASCII and they ignore the first byte. I get and I’m allowed to send only ASCII, one character one byte.<br /><br />I want to send UNICODE ----- > hex 00 65 = A in UNICODE, 65 = A in ASCII or 00 32 is space in UNICODE and 32 = space in ASCII.<br /><br />How can I manage to make the OCX’s to understand that? <br /><br />I want to be able to handle the whole screen management of the OCX’s in UNICODE like WINDOWS does so that I can, for example enter in a textbox mixed Chinese and English. This is only possible in UNICODE.<br /><br />I hope that helps you to understand this problem better and you can tell me how to manage that.Michael Farnbauerhttp://www.gmx.denoreply@blogger.comtag:blogger.com,1999:blog-19326029.post-47746916317882885212009-09-06T01:10:23.965+02:002009-09-06T01:10:23.965+02:00I need help for ocx-elements......
I will furnish...I need help for ocx-elements......<br /><br />I will furnish the ocx-elements with unicode basically.(it takes 2 bytes for one character basically)What I lack is , that the textbox know, that she get unicode and that the textbox shows that correct and that the textbox gives unicode back basically.<br /><br />Maybe someone will have a idea, and i will be happy ;-)<br /><br />Thanks for the answers.<br />FranzFranzhttp://www.diva-software.denoreply@blogger.comtag:blogger.com,1999:blog-19326029.post-66606924018457265202009-09-05T13:50:06.794+02:002009-09-05T13:50:06.794+02:00How i can support from gfawin23.ocx to unicode? so...How i can support from gfawin23.ocx to unicode? so that my database can use letters from unicode? For example: Its not a problem to write in my database (latin letters) with ascii-code, but if i want to write letters from unicode, my database didnt accept it! He didnt shows the letters from unicode....What i have to do, that my database shows me the unicode-letteers like Ð, ý, Þ, ð, etc.<br />as original letters like Ğ, ı, ş, ğ, etc.???<br /><br />Thank you for your answers.<br />Franz BaldasFranz Baldashttp://www.diva-software.denoreply@blogger.com