Hyperion Entertainment Message Boards

Create a few directories in RAM:


Makedir ALL "RAM:test/foo (bar)" "RAM:test/bar (foo)"
Echo to "RAM:test/foo (bar)/foo"
Echo to "RAM:test/bar (foo)/bar"


Then try something simple as:

List RAM:test ALL FILES LFORMAT "%p%n" LFQ W

and watch it fail, stumbling on the parenthesis in the paths ...

Old cruft that's been bothering me since forever with Workbench...

With Workbench as windows, the screen background (not window, not workbench) image actually fills the screen, and the screenbar is drawn on top of it - good!
With Workbench as backdrop, the Workbench (not screen, not window ...

Same for 3.2.3

The only way to get a "file" somewhat correctly is to ask workbench about selected icons in active window, there's no way to get selected icons in _all_ windows (volumes, drawers and root), and getting "file" associated with icons left out on the workbench root windows is still ...

Windows is the extreme, “even Windows” - for small hobby OSes that don’t have to relate to enterprise demands etc this is even easier - updates can be released at once, with barely any consequences.

The frustration is in reporting bugs and get zero respons.
The frustration is in being told that ...

Oh wow - response! It’s not just whrn I type it manually, it’s also if I select a directory with the ASL reuester.

Oh, and that other annoyance with Find, that it doesn’t take the active window as path argument when called from the workbench “window” menu? Will that be fixed too? I have a work ...

More titties and beer is needed!!

Can someone please explain why it is that many (but not all!) of the binaries of 3.2.2 update are same version string as in 3.2 and 3.2.1, yet checksum and file size are different? Because they are now built with updated SDK/NDK/Toolchain, I presume - but this ...

Can confirm that this is fixed in the 3.2.2 updated.

Update for 3.2.2:

Allthough C:List has not changed, this bug has been fixed!!
(can only speculate which kickstart component that triggered it in the first place)

This annoying oddity still remains in 47.21 of the 3.2.2 update, sigh!

Bug still present in 47.21 (25.02.2023) - how is it possible that noone else complains about this rather obvious bug??!