Welcome, Guest. Please login or register.
Amiga Kit Amiga Store Iridium Banner AMIStore App Store A1200/A600 4xIDE Interface

Recent Posts

Pages: 1 ... 8 9 [10]
91
Amiga OS -- Development / Re: Amiga OS 3.2 released
« Last post by kolla on June 06, 2021, 05:35:28 PM »
So make the screen wider with Autoscroll enabled?

Cannot be done without closing and reopening Workbench screen - the point here is that this is a need that pops up and the limitation is super annoying.
92
Amiga OS -- Development / Re: Amiga OS 3.2 released
« Last post by TribbleSmasher on June 06, 2021, 05:32:48 PM »
So make the screen wider with Autoscroll enabled?

If only the window of the console is wider and offscreen, you couldn't read the text anyhow. What's the point in it?
93
Amiga OS -- Development / Re: Amiga OS 3.2 released
« Last post by kolla on June 06, 2021, 05:30:24 PM »
The use case is quite obvious - you mention console, sometimes output (and for that matter, input) is longer than console window is wide - especially when workbench screen is 640 pixels wide, and that in particular is when I - ad hoc - wish to make the console window larger than screen. In general I don’t see the point in moving windows off screen if it’s not possible to make windows larger than screen.

So when do one wish for wider consoles?
When dealing with long filenames and file comments for example.

As for radio buttons - so Windows 95 was first version of Windows with what… “radio buttons” in the menus? And Win 3.x and earlier used what… checkmarks?
94
Amiga OS -- Development / Re: Amiga OS 3.2 released
« Last post by boemann on June 06, 2021, 04:42:07 PM »

You do know that Commodore's idea (93) to use checkmarks and bullets in the menu like that predates Windows 95 - so this is actually an original Amiga concept.
Who said anything about Windows 95? Anyways OS 3.1 was released post 1993 without "radio buttons" in the menus.

(and personally I never saw the point of radio buttons, we have cycle menus (and cycle to menu) for that)

Quote
As for windows larger than screen I can only take it that you want to break every program out there that assumes this can happen. Like console and probably a lot of other programs. So while in you infinite wisdom you may think it should just be done, there are actually well thought out reasons why it would be a really bad idea. And in practice not that many people will even find it useful anyway.

I suppose that is why it is working just fine in OS4?

Seriously - when I first complained about this, Thomas said it was due to the possibility to somehow "move" windows into a position where no gadgets would be available to move it back or resize - there was ZERO explaination to how this could possibly happen, but arguing against dogma is pointless. When pointing out that OS4 manages just fine and resize windows larger than screen without any trouble, the "clarification" was that OS4 has the option to resize windows from all directions - well, now OS3 has the same, and yet here we are. And now there is a new excuse "break every program out there" - excuse me, but wtf what? Why don't those programs break on OS4 then?

Well 3.1 was a rushed job in the dying days of Commodore. So they didn't have time to do much of anything. But read the devcon notes from 93 and you will see the idea clearly described. I mentioned win95 as that is the first windows version that has this, so commodore clearly was first.

As for windows larger than screen I too didn't understand that reason about moving into a position where gadget would be unreachable, and resizable from all edges doesn't make a difference as i see it. But the reason that programs might break is certainly true for console, which allocates a buffer based on the screen assuming this is the largest buffer it hast to be prepared for. This can obviously be changed , but if console assumes this, then other programs may expect it too. Programs written for os4 are probably expected to be prepared for this - i don't know - i just know console will fail.

Now we have introduced some legacy compatibility options in 3.2 and limiting window size to screen could certainly be made a new compatibility option so in general windows could be made larger. Then we would "only" have to change intuition to handle this. The point is however that it is not a small thing, and none of us see any real value in it. I understand you do, but I have never seen any user using this on windows, so why would they on the amiga. It would just be a waste of time implementing and testing it. I would much rather spend our time on something that brings more value to users.
95
Amiga OS -- Development / Re: Amiga OS 3.2 released
« Last post by kolla on June 06, 2021, 03:04:10 PM »

You do know that Commodore's idea (93) to use checkmarks and bullets in the menu like that predates Windows 95 - so this is actually an original Amiga concept.
Who said anything about Windows 95? Anyways OS 3.1 was released post 1993 without "radio buttons" in the menus.

(and personally I never saw the point of radio buttons, we have cycle menus (and cycle to menu) for that)

Quote
As for windows larger than screen I can only take it that you want to break every program out there that assumes this can happen. Like console and probably a lot of other programs. So while in you infinite wisdom you may think it should just be done, there are actually well thought out reasons why it would be a really bad idea. And in practice not that many people will even find it useful anyway.

I suppose that is why it is working just fine in OS4?

Seriously - when I first complained about this, Thomas said it was due to the possibility to somehow "move" windows into a position where no gadgets would be available to move it back or resize - there was ZERO explaination to how this could possibly happen, but arguing against dogma is pointless. When pointing out that OS4 manages just fine and resize windows larger than screen without any trouble, the "clarification" was that OS4 has the option to resize windows from all directions - well, now OS3 has the same, and yet here we are. And now there is a new excuse "break every program out there" - excuse me, but wtf what? Why don't those programs break on OS4 then?
97
Amiga/MorphOS/AROS Programmers Forum / Re: ALS, a new graphics system - RELEASED!
« Last post by saimo on June 06, 2021, 11:04:44 AM »
Working on Follix (which uses ALS) inspired a few improvements.

v1.94 (06.06.2021)
 * Added ALS_CHECK_LAYER_INDEX[].
 * Added ALS_COPY_PALETTE_SEGMENT[].
 * Added ALS_CREATE_LAYER_AS_CLONE[].
 * Added ALS_SET_LAYER_A_AND_COLORS_FROM LAYER[].
 * Made check on layer index in ALS_DESTROY_LAYER[] and ALS_MAKE_LAYER_DESCRIPTOR[] more robust.
 * Removed check on layer index from ALS_GET_LAYER_DEPTH[].
 * Simplified ALS_OPEN_FILE[].
 * Updated manual.

https://www.retream.com/ALS
98
Amiga OS -- Development / Re: Amiga OS 3.2 released
« Last post by gertsy on June 06, 2021, 08:31:37 AM »
Quote
....What's next - ctrl+c/v as shortcut for "copy" and "paste"?

Brilliant!
99
Amiga OS -- Development / Re: Amiga OS 3.2 released
« Last post by TribbleSmasher on June 05, 2021, 07:20:02 PM »
I made an AmigaGuide from the developers' releasenotes which were updated with the 3.2NDK, attached below, the file uncompressed at about 1MB in size.
100
Amiga Software Issues and Discussion / Unofficial AIBB v6.8 patch
« Last post by SpeedGeek on June 05, 2021, 02:34:45 PM »
Unofficial AIBB Version 6.8 patch
© SpeedGeek 2021

INTRODUCTION:
This an update to the previous AIBB v6.7 patch. It has
some new code to report the CPU Revision when a 68060
is detected.

FEATURES:
- New code reports CPU revision on 68060 systems
- Runs all original AIBB code on 60000-68040 systems
- 100% PC relative Assembler code
- Patched executable is only 52 bytes larger than v6.7
- Updates version to 6.8

REQUIREMENTS:
- Amiga with 68060 CPU
- AIBB v6.7 "Update" version!
- SAS spatch tool

WARNINGS:
This patch does NOT update AIBB to fully support the
68060 CPU in the way a benchmark program written
specifically for that purpose would do. It does NOT
functionally affect MOST of the limitations of the original
AIBB code except for allowing it to run on 68060 systems.

NOTES:
The CPU Revision is reported in the System Information screen.
This patch can NOT be applied to the older non-update v6.7
version.

Here is the link:

https://eab.abime.net/showthread.php?p=1488897
Pages: 1 ... 8 9 [10]