R: AW: Studio 4.3.2.1 non-unicode on Windows – Polish Font
HI to all,
Michael
How can I call a “GetUserName” function in KERNEL32.DLL … which are the parameters…
Register DLL (‘kernel32′,’GetUserName’,’???’) Returns lvReturn
Thanks
Bye
Rocco
_________________________________
Distinti saluti. Best regards.
Rocco Dr. Ventura
WMS Analist and Software Developer
KUNVI srl – Experiences Holding – www.kunvi.it
Email: r.ventura@kunvi.it – Mobile: +39 348 5186051
—–Messaggio originale—–
Da: omnisdev-en [mailto:omnisdev-en-bounces@lists.omnis-dev.com] Per conto di Michael Mantkowski
Inviato: martedì 17 ottobre 2017 16:23
A: ‘OmnisDev List – English’ <omnisdev-en@lists.omnis-dev.com>
Oggetto: RE: AW: Studio 4.3.2.1 non-unicode on Windows – Polish Font
Hi Rudolf,
I made my 4.3.2.1 application Unicode ready in a few hours. I guess it depends on how many features you have in your system that are impacted.
The two things for me were Register/Call DLL commands and Saving Text files.
I created an internal variable call “inU” that is True if we are in a Unicode version of Studio.
Calculate inU as isunicode()
So, then you can do this for your Register and Call DLL commands.
Register DLL (‘kernel32’,con(‘GetComputerName’,pick(inU,’A’,’W’)),’JCM’) Returns lvReturn ;; Get the name of the current computer
Here is how I create a text file. This example sores the location of the last datafile the user was in. I don’t have an example of what it was before. It’s been a couple years since I did this but I do know it had to be updated for Unicode or the text files came our wonky. This type works for both Unicode and Non-Unicode.
Do FileOps.$splitpathname(pick(sys(6)=’X’,sys(215),sys(209)),lvDrv,lvDir,lvFile,lvExt) Returns lvError
Calculate lvLastDataFilePath as con(lvDrv,lvDir,’LastDataFile.ini’)
Do FileOps.$deletefile(lvLastDataFilePath) Returns lvError
Do lvFileObj.$createfile(lvLastDataFilePath) Returns lvError
Do lvFileObj.$openfile(lvLastDataFilePath) Returns lvError
Do lvFileObj.$writecharacter(kUniTypeNativeCharacters,inDataPath) Returns lvError
Do lvFileObj.$closefile()
*********************************************************************
Michael Mantkowski
ClienTrax Software
1-614-875-2245
*********************************************************************
—–Original Message—–
From: omnisdev-en [mailto:omnisdev-en-bounces@lists.omnis-dev.com] On Behalf Of Rudolf Bargholz
Sent: Tuesday, October 17, 2017 9:50 AM
To: OmnisDev List – English <omnisdev-en@lists.omnis-dev.com>
Subject: AW: AW: Studio 4.3.2.1 non-unicode on Windows – Polish Font
Hi Alain,
This is before I get anywhere near a database. I enter a polish Ł into an Omnis entry field, and Omnis converts this to an L. I guess it will have to be a Unicode conversion, but I am currently swamped in work, so I just have no idea where to find the time to do this.
Regards
Rudolf
—–Ursprüngliche Nachricht—–
Von: omnisdev-en [mailto:omnisdev-en-bounces@lists.omnis-dev.com] Im Auftrag von Alain Stouder Omnis
Gesendet: Dienstag, 17. Oktober 2017 13:30
An: OmnisDev List – English <omnisdev-en@lists.omnis-dev.com>
Betreff: Re: AW: Studio 4.3.2.1 non-unicode on Windows – Polish Font
Hi Rudolf,
I suspect this is due to using map tables.
If you use native I guess you will have all windows accepted chars in your database but your Mac clients will see strange signs.
Regards,
Alain
—
Learn something new every day!
> On 17 Oct 2017, at 13:10, Rudolf Bargholz <rudolf@bargholz.ch> wrote:
>
> Hi Rocco,
>
> Thanks. I see no other solution. Wish I had time to do this ….
>
> Regards
>
> Rudolf
>
> —–Ursprüngliche Nachricht—–
> Von: Rocco Ventura [Kunvi] [mailto:r.ventura@kunvi.it]
> Gesendet: Dienstag, 17. Oktober 2017 09:05
> An: Rudolf Bargholz <rudolf@bargholz.ch>; ‘OmnisDev List – English’
> <omnisdev-en@lists.omnis-dev.com>
> Betreff: R: Studio 4.3.2.1 non-unicode on Windows – Polish Font
>
> Hi Rudolf,
>
> so.. perhaps it’s time to pass to the Unicode version 😉
>
> I did it in june this year, from 4.2 not-unicode and… it worth the effort.
>
> (from EurOmnis conference)
>
> Bye
>
> Rocco
>
> _________________________________
> Distinti saluti. Best regards.
>
> Rocco Dr. Ventura
> WMS Analist and Software Developer
>
> KUNVI srl – Experiences Holding – www.kunvi.it
> Email: r.ventura@kunvi.it – Mobile: +39 348 5186051
>
> —–Messaggio originale—–
> Da: Rudolf Bargholz [mailto:rudolf@bargholz.ch]
> Inviato: sabato 14 ottobre 2017 18:43
> A: OmnisDev List – English <omnisdev-en@lists.omnis-dev.com>
> Cc: r.ventura@kunvi.it
> Oggetto: AW: Studio 4.3.2.1 non-unicode on Windows – Polish Font
>
> Hi Rocco,
>
> Thanks, but the problem is with the entry of text in a window field in Omnis, long before the data is sent to the database. When entering text the text is not written as it should, but rather automatically converted from Windows-1252 into the corresponding Windows-1250 characters. I was hoping someone else has had similar problems, and a solution that might avoid us being forced to convert our app to Unicode.
>
> Regards
>
> Rudolf
>
> —–Ursprüngliche Nachricht—–
> Von: omnisdev-en [mailto:omnisdev-en-bounces@lists.omnis-dev.com] Im
> Auftrag von Rocco Ventura [Kunvi]
> Gesendet: Samstag, 7. Oktober 2017 15:19
> An: ‘OmnisDev List – English’ <omnisdev-en@lists.omnis-dev.com>
> Betreff: R: Studio 4.3.2.1 non-unicode on Windows – Polish Font
>
> Try with this command:
>
> Do iSessionObj.$logon(HostName,UserName,Password,SessionName)…
> Do iSessionObj.$charmap.$assign(kSessionCharMapNative)
>
> Bye
>
> Rocco
> _________________________________
>
> Distinti saluti. Best regards.
>
> Rocco Dr. Ventura
> WMS Analist and Software Developer
>
> KUNVI srl – Experiences Holding – www.kunvi.it
> Email: r.ventura@kunvi.it – Mobile: +39 348 5186051
>
> —–Messaggio originale—–
> Da: omnisdev-en [mailto:omnisdev-en-bounces@lists.omnis-dev.com] Per
> conto di Rudolf Bargholz
> Inviato: venerdì 6 ottobre 2017 15:50
> A: ‘OmnisDev List – English’ <omnisdev-en@lists.omnis-dev.com>
> Oggetto: Studio 4.3.2.1 non-unicode on Windows – Polish Font
>
> Hi,
>
> Anyone know if it is possible to tell Omnis Studio 4.3.2.1 non-unicode to use the Windows-1252 charset instead of the Windows-1250 charset? It seems as if the Windows-1250 charset is hard-coded into Omnis on Windows.
>
> Regards
>
> Rudolf Bargholz
>
>
> _____________________________________________________________
> Manage your list subscriptions at lists.omnis-dev.com
>
>
> —
> Questa e-mail è stata controllata per individuare virus con Avast antivirus.
> www.avast.com/antivirus
>
> _____________________________________________________________
> Manage your list subscriptions at lists.omnis-dev.com
>
> _____________________________________________________________
> Manage your list subscriptions at lists.omnis-dev.com
>
_____________________________________________________________
Manage your list subscriptions at lists.omnis-dev.com _____________________________________________________________
Manage your list subscriptions at lists.omnis-dev.com
_____________________________________________________________
Manage your list subscriptions at lists.omnis-dev.com
_____________________________________________________________
Manage your list subscriptions at lists.omnis-dev.com