So here it is, my traditional Xmas card video, sketched in SketchBlock , captured with SRec at 1080p and edited in Blender. All on the X1000.

Hope you like it!

https://youtu.be/0bwDHrERv9o

@AlfredOne

Some long while back I wrote a USB driver for touch screen that overlaid the monitor, and used an infrared grid to sense the touched areas. I forget the model now. No idea if the company I wrote it for did anything with it.

Anyway I found it worked quite nicely with the smudge tool in my SketchBlock application.

The resolution was much to low to be of use with anything else.

@MartinW

There weren't until recently.

email me andy@broad.ology.org.uk

@MartinW
[quote]
I don't want to hijack your thread, but very similarly...

How about keyboard / mouse share? I'm aware of an Amiga specific program in AmiStore, but I'd like to use the same keyboard and mouse between Mac and X5000.
[quote]

Of you can adapt it MAC, I can provide the src code to the linux MKShareClient on the grounds you provide me with the working client ince compiled.

@pjs

Feel free to spread it

Hmm I just reviewed my original bug report thread on this, and the problem stopped for me when I changed to a faster card. So it could be the issue wasn't fixed as such.

@msteed

Quote:
But if I read the thread correctly you do not currently see the issue? You sdaw it with your old card? What gfx lib would you have had had installed when using that card?

It looks like a DMA / VRAM Copying bug that was fixed long ago.

What gfx.library do you have?

@imagodespira

There is as far as I remeber an enhancement request for a new CURSORPEN.

It needs updates to intuition and then all the gadgets needing it to be updated.

It's not quite as trivial as you might think at first glance.

@rjd324

The textgadget cursor and other gadgets such as the string.gadget uses the shine pen for it's background.

You can change the colour it uses in GUI prefs

Darkening the shine pen may have unintended consequences though.

Instead of writing a program why not just wrap yout command in an abc-shel call

sh -c "testit 2>&1" >raM:log

In the absense of a proper solution to redirection STderr to Stdout, what you really need is a custom PIPE: that has two inputs amd one output that can mux the output into a single stream.

"&>"

Don't name it that

Weirldy named commands will only cause issues.

The core problem with using the syntax

Command >ram:log *>>ram:log

is that you now have two streams writing to the same file. Neither stream knows what the other has written, so parts of the output will be overwritten.

To expand your simple test above.





You need to redirect stderr to stdouts stream. Not 100% sure if you can do that at the shell level.

Historicaly in AmigaDOS pre AmigaOS 4 shells STDERR and STDOUT were the same stream so no extra sysntax would be needed.

sounds like your MNG.datatype descriptor has matched against some of your ordinary png files.

Multiviewer will display a GUI when displaying sound files that has png elements in it.

There is no libdl.a because under AmigaOS you cannot use the libdl functions if you are not using dynamic linking.

The SDK *should have* a link to libdl.so (in SDK:local/newlib/lib) though to enable linking of programs that use it. A copy of the file will work as well but is then at risk of going out of sync with the installed version.

@Raziel

SVG support for icons is not 100% a bad idea but

Quote:

You would in fact lose the details of hand drawn pixel based icons as vector graphics is not suited to that, it's good at logos text and shape based gfx.

Compare dull android icons and emojis to the subtletiess of the icons sets create by Mason

A matter of taste though perhaps

@geennaam

Quote:

Later MALI chipsets well work with the PanFrost drivers, need quite a recent kernel though

I have to agree with Joerg and Tony here, attempting to traverse a list whilst modifying it has always been a bad coding behaviour, and the fact you could get away withit was just "luck". Try it with a C++ list where the equivalent node structiue is fully encapsulated and bad stuff will happen if you don't do it the right way.

But as regards to backward compatabilty, the crash is only enforced with the debug kernal, which is for developers and debugging and should not generally be used by end users.

@rjd324

Quote:

Use Objdump or similar to verify the constructor array doesn't not have any NULLs in it.

The constructor calling code, assumes the array is terminated at both ends by a NULL pointer, but in some unusual cases there can be NULL in the middle which messes it up.

good:

NULL
Const1
Const2
NULL

bad:

NULL
Const1
NULL
Const2
NULL