Tthat new version are AWESOME! Thx! I only have the problem that I can only navigate with the numpad, unfortunately, it is not possible to enter numbers. ?
Sorry for my late reply, but for the last couple of days I was working on the MorphOS port of Lite XL, with the help of BeWorlds work and some fixes of mine, to be aligned with the latest OS4 release. Hope I will make that available soon.
@jabirulo Unfortunately, there is an issue with the encodings. You see Lite XL works with unicode and our systems use ISO encodings. So I need to provide a way to convert it to unicode, and make this feature available in Lite XL. Until then, I would recommend to use it only with latin typing, or if necessary, try to write the text in notepad and paste it inside Lite XL. I know it is not intuitive, but it is a workaround.
@root I haven't experienced that issue but I will check it again. Are you sure you don't have NumLock off?
Why not use unilibdev 10.21 (os4 version only on aminet) or utf8.library one of those should work for you and then you van use utf8 text encoding and convert to/from iso codings.
@trgswe I was not aware about the unilibdev. I will have a look on that, and if it works I will prefer to use this, since there is a version for MorphOS as well.
Thank you for pointing this out.
@root I will check this out and let you know. Thanks for pointing this out.
Yes, it is with the new version. Stack increase and delete the .config works not. The programm crash right away from start. Added an crashlog on os4depot.
You don't need unlibdev or other external dependencies to convert between local charset and unicode.
Just use IDiskfont->GetDiskFontCtrl(DFCTRL_CHARSET) to get the IANA number and you can then use IDiskfont->ObtainCharsetInfo() to request a mapping table.
it crashes on PowerPC "BLR" opcode, its like the 680x0 "RTS", so my guess is corrupted stack, maybe it has run out of stack.
If that was the case it would be an ISI and not an alert.
In this case what seems to have happened is that the newlib.library dlmalloc allocator has detected an error and posted the alert 0x81000009 (AT_DeadEnd|AN_FreeTwice).
It could be that a bad memory pointer was passed to free() or maybe the memory was already freed before as suggested by the alert code. It is also possible that the magic field in the memory chunk header has been overwritten by a buffer overflow or random memory trashing.
GetDiskFontCtrl() This call is not semaphore protected. This means that several calls to this function and SetDiskFontCtrl() might cause inconsistent results. The function will not fail or crash, but the result might be near to useless in a multitasking system. This function should never be called by the average user. Its sole purpose is to provide the font preferences editor with data about the current diskfont settings. It should not be called for other purposes.
A more verbose method that should produce the same result:
struct Locale *locale;
ULONG charset = 0;
locale = ILocale->OpenLocale(NULL); /* Get default locale */
if (locale != NULL)
{
charset = locale->loc_CodeSet;
ILocale->CloseLocale(locale);
}
/* Locale autodoc says to treat zero as ISO-8859-1 */
if (charset == 0)
{
charset = 4;
}
BTW the warning note in the GetDiskFontCtrl() autodoc is mainly for the tag pairs like DFCTRL_XDPI/DFCTRL_YDPI or DFCTRL_XDOTP/DFCTRL_YDOTP where you might get a new value for the X and an old value Y if you read them while they are being modified.
@TearsOfMe I sent you a PM. Please have a look and let's talk about how we can solve those issues.
@root I have already a fix about the Numpad and will be included in the next release.
@salass00 Thank you for your recommendation.
Yesterday I spent the whole evening looking at that and what happens when someone changes the keymap to write in a different language, or even by using a modification key to do the same.
Unfortunately, when a key is pressed, SDL doesn't provide (or I didn't find it) any information about the keymap, so I can't get the difference between pressing a key in a different keymap layout and the default English.
Also, the FreeType library is involved with the written character, which is using Unicode encoding. I tested it with some other encodings but unfortunately, that didn't work.
But there is a way where the project gets the different keymap info, because when you switch to another one, other than the English, and type something then nothing outputs in the editor. So, I need to figure out where this happens, although I guess it is in the FreeType library. So, if I am thinking that well, I need to give to the library the character equivalent in Unicode somehow. So I am searching for how exactly I can do that.
I am still investigating this. Any ideas are welcome.
Nothing to add to the technical discussions here, I just wanted to say Thank You for your hard work - this is one of the best things to happen to OS4 in a long time. I've already switched over to LiteXL2 for all my Amiga development and it's a game-changer. Amazing stuff!
My Amiga blog: markround.com/amiga My hardware: X5000 running OS4.1; A1200 Vampire V1200v2, KS 3.1.4
@mdr You can't imagine how much happy that makes me. Hope you enjoy it. Of course more updates will come, and if you experience issues, please do not hesitate to contact me.
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TuneNet forum
Unsatisfactory Software forum
