Hollywood forums

Changed this a little, the error code is now user-configurable: - New: Added the ERRORCODE console argument/tooltype; this argument allows you to set an error code that Hollywood should return in case an error occurs; this allows you to react on certain error codes when embedding Hollywood in batch ...

Standard JSON-parser should not support storing or evaluating code. Generally it's a bad idea and should only be done with trusted JSON, as it would allow injecting malicius code into your game. Good point. It's still supported,though, but only as some proof of concept sort of. I'd also advise agai...

Ant hope to have an updated version of avcodec ? That's unlikely. The problem is 68k compilers. The code quality of 68k compilers is very low nowadays which means that you have to manually find bugs in the code generator and implement workarounds. It was already very difficult to create a stable 68...

Sure, that's possible. You can register new event types using hw_RegisterEventHandlerEx() and then post events to the event queue using hw_PostEventEx().

Try to cut your project down to an MCVE and then post that here...

By the way concerning avcodec.hwp I start from some MOV files, that avcodec is supposed to read, however I receive a message that this format is not supported. Yes, that can happen. Keep in mind that avcodec is based on an ffmpeg version from 2010 and MOV is only a container format that could use e...

avcodec.hwp currently doesn't export any savers but only loaders for video formats. That's why you can't save in MP4 with it currently.

I don't quite get this one. Do you think #ATTRACTIVE should return FALSE in case a GL Galore script runs in fullscreen but that screen is not the frontmost screen?

Sure, in the long run this is planned but it's a lot of work because the Amiga backends are currently very much tied to 32-bit so lots of things would have to be changed. Maybe if MorphOS also went 64-bit on an ARM platform or something like this, I'd have more motivation because AROS is only used b...

I'm afraid there's probably no way around implementing a different logic between Android and the desktop platforms on your end because what you're seeing is how Android's listview widget behaves. I don't think it's possible to impose a different logic onto it.