Due to bugs in the last version I stepped back to one of previous sources and started to carefully add missing features step by step.
Additionally I rearranged the GUI.

Can you test the particular downgraded versions?
To avoid mix-ups I described what parts don't work and what I succesively added.

Dec/hex/bin String field doesn't work as input for now. HTML name String field as well.
Both strings have no limitations as for range of input chars and number of chars.
Hexaco_2017-06-10

Added: HTML String field work as an input while selecting a name from the list as well as while typing in by hand.
Hexaco_2017-06-10_1

Added: hex/dec/bin String field now works as an input. Additional it has limitations of number of chars to input and of range of chars. Limitation change according to the cycle gadget state.
Hexaco_2017-06-10_2

icon

_________________
I miss draggable screens in MorphOS... and do you? I know I'm in a minority unfortunately.

@r-tea

Quote:

Can you test the particular downgraded versions?

Done!

Quote:

Hexaco_2017-06-10

This has again the old character bug. There is crash in what looks like string compare code that is trying to compare pointers with the number 1 and 2. They need the string pointer, not the string character.

Dragging sliders triggers it or using the hex/dec/bin cycle gadget.

Quote:

Hexaco_2017-06-10_1

This immediately crashes in a stack operation. The code tries to allocate around 2K for some stack and fails. Looks like it was in a MUI routine. It doesn't always happen. If Yam or Hexaco has been open it turns up. You may have a memory leak or MUI resource you are not freeing. There is now a copy frozen on my screen.

It also exhibits the character bug.

Quote:

Hexaco_2017-06-10_2

Same as above.

@Hypex

What OS? AmigaOS4.1?

I suspect lamps handling loop, and I prepared a version where I got rid of it:
Hexaco 0.9.8 no lamps

icon
Does it still crash?

Last edited by r-tea on 13-Jun-2017 at 12:22 AM.

_________________
I miss draggable screens in MorphOS... and do you? I know I'm in a minority unfortunately.

@r-tea

Yes OS4.1. You'd have to write a string into a null pointer before you crashed OS3 that hard.

Quote:

Does it still crash?

Yes. Sliders are okay. But as soon as I try and enter any text it goes boom. It crashes in the kernel, so it calling a routine along the way that deals with pointers. It could be an Exec routine working with nodes, for example.

The previous ones, look like they are passing characters to a StrCmp() like routine.

But I wouldn't worry about the lamps. Just need to figure out any char or string compares and see if it is done correctly. Using EDBG is handy.

Last edited by Hypex on 14-Jun-2017 at 03:28 PM.

As for lamps, it had a really bad comparison function which caused hits. I have fixed it.
As for entering text (I suppose while dec: is active) I have fixed the parsing procedure.
Hexaco 2017-06-14_1
icon

_________________
I miss draggable screens in MorphOS... and do you? I know I'm in a minority unfortunately.

@r-tea

The latest version seems to work fine under MorphOS at least. Except if you select Aqua, you get Cyan (didn't test them all, but happened to try that).

One way to test programs little better under MorphOS is to use the Wipeout tool, which is included in the SDK. It will detect memory trashing.

To use it:
1) Launch SDK:Tools/logtool
2) Run SDK:Tools/Wipeout
3) Test your program and see if there comes any hits to the logtool window

For example, I got this with the earlier version of Hexaco when quitting the program after some testing: http://jpv.wmhost.com/testi/hexaco_wipeoutlog.txt

But as said, the latest version seemed to work fine with a quick test and didn't get any Wipeout hits.

_________________
- The wiki based MorphOS Library - Your starting point for MorphOS
- Software made by jPV^RNO

The point I'm askin here on AW.net is that I much need to test it under AmigaOS3.x and 4.x.
MorphOS tests I'm able to do myself. Hexaco is developed on MorphOS machine.

_________________
I miss draggable screens in MorphOS... and do you? I know I'm in a minority unfortunately.

@r-tea

Quote:

r-tea wrote: The point I'm askin here on AW.net is that I much need to test it under AmigaOS3.x and 4.x. MorphOS tests I'm able to do myself. Hexaco is developed on MorphOS machine.

Yea, I just wanted to make sure you know to use Wipeout. As it looked that some bugs weren't noticed under MorphOS from the normal debug log or in normal use, but you still can spot them with Wipeout (== it happens under MorphOS too even if it doesn't crash immediately). It makes it easier if you can catch some bugs already on MorphOS before getting crash reports from other platforms.

_________________
- The wiki based MorphOS Library - Your starting point for MorphOS
- Software made by jPV^RNO

@jPV

BTW, are you able to make some tests on classic Amiga with AGA/ECS for me? I need to know what number of WB screen colors needs Colorfield.mui class at least to activate itself.

_________________
I miss draggable screens in MorphOS... and do you? I know I'm in a minority unfortunately.

@r-tea

Maybe, if I finish unpacking of my Amigas from the last weekend's LAN party trip :) Maybe I'll do that today...

_________________
- The wiki based MorphOS Library - Your starting point for MorphOS
- Software made by jPV^RNO

@r-tea

Quote:

r-tea wrote: @jPV BTW, are you able to make some tests on classic Amiga with AGA/ECS for me? I need to know what number of WB screen colors needs Colorfield.mui class at least to activate itself.

On an AGA machine (A1200) with the original MUI 3.8:
8 colors = color field disabled, 16 colors = color field works

And the same if I boot in OCS mode, it works with 16 colors.

Last edited by jPV on 17-Jun-2017 at 02:20 PM.
Last edited by jPV on 17-Jun-2017 at 02:19 PM.

_________________
- The wiki based MorphOS Library - Your starting point for MorphOS
- Software made by jPV^RNO

@r-tea

Regarding the fixes in Hexaco 2017-06-14_1 there are still issues. I can see some string contents being passed as a pointer. For example a pointer passed was "011," or $3031312C. So somehow the first four bytes of of the string were read in as a long word.

I can also see characters passed as pointers, like pointers of $31 and $32, so number 1 and 2 in ASCII were sent as pointers.

Now if we had some kind of debug tool that could decode a line number from an offset in a 68K binary that would be good. OS4 has one for binaries. AmigaE I don't know.

Last edited by Hypex on 18-Jun-2017 at 06:10 PM.

@Hypex

Quote:

Regarding the fixes in Hexaco 2017-06-14_1 there are still issues. I can see some string contents being passed as a pointer. For example a pointer passed was "011," or $3031312C. So somehow the first four bytes of of the string were read in as a long word. I can also see characters passed as pointers, like pointers of $31 and $32, so number 1 and 2 in ASCII were sent as pointers.

Is it while entering values by hand (and then hitting enter/return), or while moving sliders?

_________________
I miss draggable screens in MorphOS... and do you? I know I'm in a minority unfortunately.

@r-tea

Quote:

Is it while entering values by hand (and then hitting enter/return), or while moving sliders?

Yes entering values. It happened in the Hex gadget. Activating it by clicking it. Backspace, enter number, return. Off it goes.

The routine looks like it is taking an index, scaling it up, adding it to an offset and then to a pointer. Then reading from that. So one step too far since it forms a string pointer but then treats the string as a pointer.

I've gone through your code and it looks fine. I think the get_col() routine is crashing for my testing. Narrowing it down.

Looking into writing a program that can read debug info from E binary and decode an offset into a line number.

@jPV

Quote:

On an AGA machine (A1200) with the original MUI 3.8: 8 colors = color field disabled, 16 colors = color field works And the same if I boot in OCS mode, it works with 16 colors.

Can you provide me the version number of your Colorfield.mui class?

_________________
I miss draggable screens in MorphOS... and do you? I know I'm in a minority unfortunately.

@r-tea

Quote:

r-tea wrote: @jPV Quote: On an AGA machine (A1200) with the original MUI 3.8: 8 colors = color field disabled, 16 colors = color field works And the same if I boot in OCS mode, it works with 16 colors. Can you provide me the version number of your Colorfield.mui class?

Colorfield.mui 19.8 (12.02.1997)
It's the same which is found from the mui38usr.lha archive.

I guess it depends what pens you have locked and is there any free ones to use. MUI autodocs says it requires an exclusive pen...

_________________
- The wiki based MorphOS Library - Your starting point for MorphOS
- Software made by jPV^RNO

Thank You.
Just to complete the thread, there is final version 1.0 available on Aminet.
http://aminet.net/package/util/wb/Hexaco_1.0
In the readme file I have mentioned the problem with low colour palette screens and with PullPalette patch.

_________________
I miss draggable screens in MorphOS... and do you? I know I'm in a minority unfortunately.

After a positive feedback from Lazi I decided to do a few improvements, and there is 1.1 version of Hexaco. A small utility to help to generate and hndle colour RGB codes.
You can find it on Aminet.Would be great to get a feedback from you how it works or if it works at all. Especially I need tests under AmigaOS 3.x and 4,x.

_________________
I miss draggable screens in MorphOS... and do you? I know I'm in a minority unfortunately.

@r-tea
I tested Hexaco 1.1 on my X5000 with OS4.1FEu1. Running Hexaco after booting and before starting certain other MUI programs works. If I start Odyssey or some other MUI programs before starting Hexaco, then Hexaco partially opens it's window and freezes. I won't be able to test again until June but I thought I'd let you know there is a potential problem.

_________________
X1000 with 2GB memory & OS4.1FE

Thanks Xenic. Can you test v1.0 for comparison?

Is there anyone who's able to do some tests under AmigaOS 3.x?

_________________
I miss draggable screens in MorphOS... and do you? I know I'm in a minority unfortunately.