@Samurai_Crow

FYI, OldOpenLibrary() still works on 68K for OS4, but it obviously doesn't exist in the interfaces.

I tried it out for sh*ts and giggles about a year ago.

Does CMake need to be run under a unix-like environment (e.g. sh CMake)

<<< Double Post >>>

@Raziel

I reported it in the with the enhancer software folks.

@jabirulo

Thanks for the diagnosis. I was getting the same weird freeze with DiskImageGUI and adding a texture fixed it.

FYI. Since the InfoWindow class in the Enhancer Pack caused me a similar lockup problem I decided to retest it with a texture set in Prefs ... and that also resolves that problem. It works fine now too.

Hopefully that helps anyone else out with similar issues.

@kilaueabart

lol. Fair enough ... sometimes I just can't help myself. I'll let the 30 year gap slide

@Severin

Lol.

He would have been installing actual font cases in real drawers back then. Maybe his workbench is still going strong.

Thanks for putting up that video. For people who have no clue how to use video editing software (i.e. me) it gives some inspiration to have a go.

Cheers!

@sacc-dude

I don't know about the SAM460, but I know that I need a PS/2 mouse to get to the early boot menu by holding down both mouse buttons. It never worked for me with USB.

@LiveForIt

Fair points, but I still think (and hope) that apart from a few potential demos, it is unlikely.

The two things that do stick out to me are the mouse/joystick button tests and accessing Paula directly. Those might be just a bit too tempting.

Anyway, that could happen today with developers who already own OS4.1 Classic.

@LiveForIt

I wouldn't think there would be much point in specifically writing a PPC os4.1 app and then proceeding to hit the AGA chipset. May as well just write for 3.x in that case if that's what you want to do. I don't reckon that will be an issue.

My 2 cents.

I reckon it will be a good thing if OS4.1 was able to be emulated on WinUAE. I always worry that when my (now 10 year old) hardware eventually goes all time investment in OS4.x goes out the window, so I tend to write for 68k because I know I will be able to keep using it in future. If there was OS4.1 classic emulation I would be more inclined to write things for it as I know my time investment is not gone when the machine fails.

I think the emulation will happen on WinUAE because even if Toni doesn't have interest in that bit, I'm sure someone else with those skills will.

Like many, I would love to buy an X1000 but it just costs too much for me to afford (and I really tried to kid myself last month too!!!).

My personal opinion is that 4.1 should be the last version to work on classic anyway and 4.2 should break that tie, working on the future (hopefully) more affordable machines. Since 4.1 was current for so long, it doesn't hurt to target that version for a while, even using emulation, anyway.

If WinUAE supported Classic 4.1 I'd buy a copy for sure.

Finally, Hyperion could not be expected to write drivers for software that they don't support. It is up to the emulation to be right and/or specific drivers to be written for the emulation by interested parties. If Hyperion happens to become one of those interested parties, all the better.

Phew! I think that's enough

@mechanic

I think "beginner what?" is a good question.

It might be a good idea to have several packages which would all contain the agreed-apon basics that are handy under all configurations and then their own package-specific apps.

Then there could be:
Musician Beginner Pack
Office Beginner Pack
Graphic Artist Beginner Pack
Developer Beginner Pack
... etc.

Those packages are more likely to attract those groups than one general "beginner" package.

I've seen that when looking at qt apps too.

It appears that they are not taking the window border height and width into account when rendering ... just going with 0,0. I suspect it may be in the qt library but check the docs to see if you are supposed to account for it.

@zzd10h

What messages would you send? Each app responds to different ARexx messages?

Health is always #1. Hope it all heals soon.

@broadblues

Oh, I didn't realise that ... handy.

@Antique

Are you trying to do a requester similar to the way it's done on MacOS X where the requester might not fit entirely in the parent window?

@nbache

I completely agree with everything you say. Forcing UI control like that is a quick way to get your program uninstalled. The position of windows should be under the control of the user. It is their Workbench after all, not the developer's ... however there is a way to prevent moving the window. Just don't provide a drag bar, though that would be in place for the window's entire duration.

Congratulations. Looks fantastic.