Anyone know what would cause a crash in AmigaOS 3.X (from Cloanto's Amiga Forever)

[Nightfox]

All this GUI magic happens in the gui.c file in the source if anyone wants to have a look

[Don_Adan]

Then perhaps can be trashing memory problem. You can alloc more memory that is necessary for work.
f.e alloc 2MB fast, if You need only 100KB.
Fill this memory with ID, f.e "WTWT" And save to file when quit from program.
Later look at this memory.

[Nightfox]

well I dont know what is being trashed right? im doing a whole bunch of individual allocations with AllocVec() for whatever needs memory

[alexh]

Originally Posted by Nightfox

Actually I've seen a lot of messages from sad people wanting to run AmigaGPT on AmigaOS 3.1 which doesn't have ReAction

Isn't ClassAct the AmigaOS 3.1 predecessor of ReAction? Most AmigaOS3.1 users will have ClassAct installed. It might be easier to back-port to ClassAct than MUI

[Nightfox]

but won't the ClassAct gadgets be yet even older and have less functionality and more bugs? sounds like a nightmare

[alexh]

Probably but it was you who suggested supporting AmigaOS 3.1 and ClassAct would probably be quicker/easier than MUI.

[Nightfox]

is MUI honestly really that bad? I was under the impression its the go-to GUI library for Amiga dev and is what almost everyone is using

[Thomas Richter]

It is at least unmaintained.

[alexh]

It was far more widespread than ClassAct. But you had to have both if you wanted to be able to run "everything".

You did the right thing choosing ReAction. Encourage users to upgrade to AmigaOS 3.2

[Nightfox]

Oh man wouldn't it be amazing if some of the geniuses in this forum could band together and create a whole new GUI library with modern features compatible with 3.1->4.1

If I was smart enough I'd tackle that on my own but I'm not. I'm still getting into grips with the fundamentals of BOOPSI

[Thomas Richter]

Originally Posted by alexh

Isn't ClassAct the AmigaOS 3.1 predecessor of ReAction? Most AmigaOS3.1 users will have ClassAct installed. It might be easier to back-port to ClassAct than MUI

Yes and no. ClassAct provides (and provided) a lot of gadgets and classes, but reaction was more than that - it was/is a library that created from an abstract description a "classact"-based GUI. This is the reaction.library. This is a copyright of a third party and thus not part of 3.2, though the classact gadgets are.

[Don_Adan]

Originally Posted by Nightfox

well I dont know what is being trashed right? im doing a whole bunch of individual allocations with AllocVec() for whatever needs memory

Then add f.e 1000 or 5000 or 10000 bytes bytes for every allocation (remember to free more memory too) and check if it still crashes.
Simple, alloc more memory than You need, or think than You need.
Or use MMU tool.

[Nightfox]

Hm sure why not? When I’m in next a dev mood again I’ll search through every AllocVec() and make it allocate 10x more than it needs. I’ll see if this at least narrows it down to a memory problem

[Minuous]

Originally Posted by Don_Adan

3.X has the latest versions of Amiga components, I think.

Alas not, see screenshot...

Originally Posted by Nightfox

Oh man wouldn't it be amazing if some of the geniuses in this forum could band together and create a whole new GUI library with modern features compatible with 3.1->4.1

No need for yet another GUI library. The root problem is that many Amiga users for some reason insist on using obsolete buggy versions of things, and are then surprised that they don't work properly. Which does make we wonder why I bothered fixing all those bugs in the first place.

[alexh]

Originally Posted by Minuous

Alas not, see screenshot...

Interesting. I thought this discussion was about the 3.X Kickstart ROM?

But actually it's actually about 3.X AmigaOS/Workbench install?

[Snoopy1234]

Amikit loaded with Amiga Forever has rom v45.66 and WB v45.3 which is 3.x rom and OS3.9 BB2 equiv respectively. The Amiga Forever install includes AROS elements to confuse the lay person.

[meynaf]

Originally Posted by Nightfox

Oh man wouldn't it be amazing if some of the geniuses in this forum could band together and create a whole new GUI library with modern features compatible with 3.1->4.1

What do you need exactly that regular GadTools does not provide ?

Originally Posted by Nightfox

If I was smart enough I'd tackle that on my own but I'm not.

I've started doing mine. It is a game of designing something, trying to implement it, then discover the host OS not only does not provide the relevant tools but also goes in the way.
So ok, i want it to be usable outside of Amiga world so it often goes against the guidelines, but nevertheless.

Originally Posted by Nightfox

I'm still getting into grips with the fundamentals of BOOPSI

Before going to Boopsi, you can start with a simple paint program and draw it by hand, just to see how it has to look like. If you want modern features this may be more difficult than it seems.

[Nightfox]

Originally Posted by meynaf

What do you need exactly that regular GadTools does not provide ?

texteditor.gadget is a big one. It's not even fully implemented in its AmigaOS 3.2 form. Some features in the autodocs I dont think are even implemented yet like for example it says you can use escape sequences to change the pen but I can't get that to work at all

I dont think regular gadtools has anything super cool like layout.gadget either

[Minuous]

Originally Posted by Snoopy1234

Amikit loaded with Amiga Forever has rom v45.66 and WB v45.3 which is 3.x rom and OS3.9 BB2 equiv respectively. The Amiga Forever install includes AROS elements to confuse the lay person.

Its version.library might claim V45.3 but it is certainly not equivalent to OS3.9 BB2, as I demonstrated in my previous post.

[Nightfox]

yeah I think it must be the old .gadget files having some bug or something causing a total crash. I have had to change my code a bit in order to do backwards compatibility with older ROMs but that was mainly for exec.library calls