A new editor for AmigaOS 4 is in the works

@Capehill

Quote:

Yeah, I already have that moved for the next release. Thank you for mentioning it.

@TearsOfMe

Quote:
I get the same crash at program startup on my emulated OS4 system. My crashlog looks exactly the same.

@walkero

The system is WinUAE running OS4.1 FE Update 1. Perhaps there's something that requires Update 2?

@trixie
To be honest, although I haven't tried it yet, it should work fine in update 1. I have an emulated environment somewhere. I will give it a try and let you know.

@walkero

I tried to test this program on a 16-bit WB screenmode and then it crashed similarly than TearsOfMe reported. Looks like some nullptr issue.

Do you know what this is:

module lite at 0x7E2C51C8 (section 0 @ 0x51A4)

@Capehill
Let me have a look and let you know. But it shouldn't crash just because you started it in 16bit.

Try to remove the .config file and test it again.

Yesterday I released a new version of LiteXL v2.0.3r2, which brings some fixes and for the first time the MorphOS version to the public.

You can download it from https://git.walkero.gr/walkero/lite-xl/releases/tag/v2.0.3r2
and soon from OS4Depot.

This release brings you the following:

### Added
- First public MorphOS version released

### Changed
- Merged source code for both AmigaOS 4 and MorphOS
- Moved the declaration of the $VER and $STACK for the AmigaOS 4 version,
so to happen only once (reported by capehill)

### Fixed
- Fixed the usage of NumPad (reported by root)

@walkero

Any chance to introduce a scrollbar?

@samo79
What do you mean? There is a scrollbar.

@walkero

Quote:
Not on my system

There is a small scrollbar at the side of the page. it is not part of the window, but there is absolutely a scollbar. You don't need actually to click on it to grab it with your mouse. Even a few pixels further can grab it.

Now if you speak for a window scroll bar, I am not sure I am able to do it it, but will check this out. But since the application uses SDL I am not sure how easy is to get that and assign it to the window border.

Also, what will happen if you have multiple files opened in different positions (left, right and bottom)? That would need to change on the fly the window scrollbar based on the actively editing file, which might not make sense.

The scrollbar is there bit too thin, if you want it wider, just edit

data/core/style.lua

and the 6th line should be:
style.scrollbar_size = common.round(4 * SCALE)

and change (f.ex) to:
style.scrollbar_size = common.round(10 * SCALE)

or choose you another value: 12, 20, ...

@jabirulo
Thank you for this tip. That's one way to do it, but in a future update, you lose it. Please consider doing that in the config file. It is always better to not touch the editor code unless you really have to.

Open your configuration file by clicking on the cog icon at the toolbar (bottom left, 6th icon) and add the following line at the end of the file, and then save it.

style.scrollbar_size = 10

Bigger number, bigger scrollbar.

This way, you can transfer the .config folder to a new installation (i.e. a new release) and have everything as they were before.

@walkero

THX for tip
Restored value on style.lua and using now in init.lua:

style.scrollbar_size = 10 * SCALE

@walkero

I missed this topic :) so, thank to afxgroup for sharing link for this topic on my question for text editor for os4 with html syntax highlighting.

Great pice of sw with nice looking gui, fast.. - very useful if you ask me!

Thank you on this great app!

@voodoo
I am glad it is useful for you and you liked it. I find it really convenient, and I do all my development work using that. This means that it is easier to find bugs and fix them. I had some fixed today and will continue working on it.

Since I updated the newlib via AmiUpdate yesterday LiteXL is crashing with a GrimpReaper.

@DJBase
Try to delete the .config folder under the LiteXL folder and try that again, and please let me know if it works.

I am working on a new version with a few fixes. If it doesn't work I will push it to do it as soon as possible.

Works fine here without any problems - new string.gadget and newlib.library installed.
Maybe wrong version installed?

@walkero

Quote:

Does the trick, working again.

Probably was one of the project paths. The new release will have a few fixes to prevent such issues happening.
Thank you for testing it and using this editor