Welcome, Guest. Please login or register.
Amiga Kit Amiga Store Iridium Banner AMIStore App Store A600 Memory

AuthorTopic: Os 3.1.4 - List of bug fixes and changes by component  (Read 22351 times)

0 Members and 1 Guest are viewing this topic.

Offline Thomas Richter

Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #150 on: January 15, 2019, 06:46:39 AM »
I didn't  update this thread for a while due to lack of time, and maybe I forgot one thing and another. So here is another tiny change that will make live hopefully easier: The icon.library.

This is a version derived from the 3.9 version, but with two small changes. For 3.9, the icon.library allowed to configure the "maximum file name size" so it knew where to cut off names in case a ".info" for the icon has to be attached. This feature is gone.

Why?

Well, actually, it is no longer required, and it was a bad idea. It is a bad idea because the user can hardly know how long the file names are allowed to grow, and even worse, this maximum size depends on the file system the icon.library is working with, so it cannot be "correct" for all combinations. If you had an (old) CrossDOS version in the system, then the file name limit would be "8" (the .info is mapped to .INF by the 3.1 version of CrossDos). You surely don't want to set this limit to 8 just to be able to use CrossDos.

So, new rules apply. The icon.library does not limit the file name size at all. Instead, it now always checks whether it could create icons correctly under the name you gave them, and it checks before writing a .info file whether this file name possibly conflicts with somthing that is already on disk - conflicts because the file name of the icon and the file name of something else become identical after truncating to the maximal length. And this truncation is the job of the file system.

So what is the "maximum file name size" in the workbench dialog good for? It is really only cosmetic. The only thing this does is that it limits the maximum size the input dialogs of the workbench take, nothing more. If a program attempts to create a longer file name, that's all good, all provided the icon.library can create such a file and the file is different from the base (i.e. non-icon) file.

When renaming files, the workbench has a heuristic how to truncate file names for the "Copy_Of_" renaming of files. It also tests whether it can create a unique name by prepending "Copy_Of_", and since it cannot test all possible lengths of file names, it checks for some typical maximal file names. 30 characters for DOS\1 through DOS\5, 54 characters for DOS\8 and 106 characters for DOS\6 and DOS\7.

So no need to fiddle with the maximal file name size at all - it's all automatic.

Another change is this "put icons to fast" setting of Os 3.9. That's also gone for good. Again, because the user cannot know whether the graphics system of the screen the workbench is running on supports this option, as it may depend on the screen mode as well. It is an unwise idea to delegate a decision to a user for something the user, in general, cannot know, so the switch went away. Instead, the workbench runs a small test when opening (or re-opening) its screen whether icons can be put into fast memory - and if so - it simply does it. No need to configure anything, it's automatic.

Finally, how do you move icons to fast memory? Well, for graphics cards, this is what happens already automatically. For native systems, I *do not* recommend FBlit as this program is known to cause multiple problems as its patch set is incomplete and has defects. There are two options: Either, you run the native (AGA) driver of Cybergraphics, or you run the native driver of P96.

There is a P96 driver for the ECS/AGA chipset? Yes, there is. Check Aminet. A relatively recent P96 version is sufficient. With P96 and this "driver" installed, icons will go to fast memory.
Frankly, it's not much of a driver, but it does exactly what you want it to do.
 
The following users thanked this post: Tygre, First Ninja, NinjaCyborg

Offline utri007

Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #151 on: January 15, 2019, 12:38:51 PM »
For everyone, FBlit sources :

https://github.com/SamuraiCrow/fblit

FBlit is a hack, but it benefits are so visible that many of us uses it. With 68040 cpu and correctly configured FBLit you wil get smooth scrolling hires interlaced screens. 640x512(400)

So playing Napalm in hires interlaced screen is possible without jerky scrolling.

As genrally FBLit is easy to install, if you got problem 99% is that you didn't copy configuration file to right place.

 
ACube Sam 440ep Flex 800mhz, 1gb ram and 240gb hd and OS4.1FE
A1200 Micronic tower, OS3.9, Apollo 060 66mhz, xPert Merlin, Delfina Lite and Micronic Scandy, 500Gb hd, 66mb ram, DVD-burner and WLAN.
A1200 desktop, OS3.9, Blizzard 060 66mhz, 66mb ram, Ide Fix Express with 160Gb HD and WLAN
A500 OS2.1, GVP+HD8 with 4mb ram, 1mb chip ram and 4gb HD
Commodore CDTV KS3.1, 1mb chip, 4mb fast ram and IDE HD
 

Offline utri007

Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #152 on: January 15, 2019, 10:58:33 PM »
Picasso 96 AGA native mode driver tested. I'm going to continue use it and forget FBLit.

Chip ram is saved equally and speed seems to be OK, tested Foundation and Napalm. Screen is scrolling, not a jumping around.

What would be preformance benefits of using this?



ACube Sam 440ep Flex 800mhz, 1gb ram and 240gb hd and OS4.1FE
A1200 Micronic tower, OS3.9, Apollo 060 66mhz, xPert Merlin, Delfina Lite and Micronic Scandy, 500Gb hd, 66mb ram, DVD-burner and WLAN.
A1200 desktop, OS3.9, Blizzard 060 66mhz, 66mb ram, Ide Fix Express with 160Gb HD and WLAN
A500 OS2.1, GVP+HD8 with 4mb ram, 1mb chip ram and 4gb HD
Commodore CDTV KS3.1, 1mb chip, 4mb fast ram and IDE HD
 

Offline utri007

Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #153 on: January 16, 2019, 11:02:26 AM »
Would it be possible to make this liek a screen mode? If it is used all PAL screens, it seems to slow down games like Quake?
ACube Sam 440ep Flex 800mhz, 1gb ram and 240gb hd and OS4.1FE
A1200 Micronic tower, OS3.9, Apollo 060 66mhz, xPert Merlin, Delfina Lite and Micronic Scandy, 500Gb hd, 66mb ram, DVD-burner and WLAN.
A1200 desktop, OS3.9, Blizzard 060 66mhz, 66mb ram, Ide Fix Express with 160Gb HD and WLAN
A500 OS2.1, GVP+HD8 with 4mb ram, 1mb chip ram and 4gb HD
Commodore CDTV KS3.1, 1mb chip, 4mb fast ram and IDE HD
 

Offline Thomas Richter

Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #154 on: January 16, 2019, 11:09:10 AM »
Would it be possible to make this liek a screen mode? If it is used all PAL screens, it seems to slow down games like Quake?
Currently, no. But if you want to disable it for a particular application, you can do the following:
Code: [Select]
setenv Picasso96/DisableAmigaBlitter No
setenv Picasso96/PlanesToFast No
put that into a small shell script and run upfront the application. (Hoping that I got the spelling right).

Offline H_Celine

Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #155 on: January 24, 2019, 07:08:52 PM »
I didn't  update this thread for a while due to lack of time, and maybe I forgot one thing and another. So here is another tiny change that will make live hopefully easier: The icon.library.

This is a version derived from the 3.9 version, but with two small changes. For 3.9, the icon.library allowed to configure the "maximum file name size" so it knew where to cut off names in case a ".info" for the icon has to be attached. This feature is gone.

Will the .h and .i files form NDK3.9 work against 3.14 icon library? If not, is the 3.1.4 updated files available somewhere?
So far I'm using NDK3.1 + Handler3.1.4Doc.lha + "exec/execbase(.h|.i)" from NDK3.9. Is this correct, given what is available?
 

Offline Thomas Richter

Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #156 on: January 24, 2019, 09:11:53 PM »
Will the .h and .i files form NDK3.9 work against 3.14 icon library?
That's right, they will. Nothing changed. Well, icon.library had an option to set the "maximum file size". That is gone. Icon.library knows better itself how long a file can grow, there is nothing the caller has to tell. There (still) is an option to set the icon memory type. That remained unchanged, but you do not want to set this yourself. Workbench knows better whether icons can go into fast ram or not, and you really really do not want to tell otherwise as side effects may include trashed memory (actually, that was a particular design problem of 3.9 - namely that the end user had to tell something he could barely know as non-expert).

So far I'm using NDK3.1 + Handler3.1.4Doc.lha + "exec/execbase(.h|.i)" from NDK3.9. Is this correct, given what is available?
That is correct, indeed. We are "a bit behind", and yes, there should really be a new set of includes & autodocs (not "that new", but - you get the point). But, at present, 3.1.4.1 has priority, and as soon as this is out of the door, I keep checking for the includes.

 
The following users thanked this post: H_Celine

Offline H_Celine

Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #157 on: January 24, 2019, 09:29:40 PM »
One more question: How does newicon.library fit into this, or does it not? (I never used newicons, so I do not know how it used to work, but the codebase in question needs it.)
« Last Edit: January 24, 2019, 09:34:41 PM by H_Celine »
 

Offline Thomas Richter

Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #158 on: January 25, 2019, 07:32:05 AM »
One more question: How does newicon.library fit into this, or does it not? (I never used newicons, so I do not know how it used to work, but the codebase in question needs it.)
Frankly, I don't know. It's some third-party component I don't have and I don't use, and 3.1.4 does not require to operate. It does support more colorful icons out of the box.
 

Offline H_Celine

Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #159 on: January 25, 2019, 08:55:17 AM »
Reason I am asking is it was not 3rd party in 3.9, and the codebase in question was originally compiled against that version. And it seems version included with 3.9 does not like 3.1.4(not conclusive, still testing).

Edit: Also; the 3.1.4 Prefs/Workbench has a toggle for NewIcons.
« Last Edit: January 25, 2019, 09:20:32 AM by H_Celine »
 

Offline Thomas Richter

Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #160 on: January 25, 2019, 09:34:11 AM »
Reason I am asking is it was not 3rd party in 3.9,
This would surprise me. 3.9 certainly did not include something called "newicon.library". Its icon.library supports "newicons", and so does the 3.1.4.1 version as it is a later version of the 3.9 icon.library.

Edit: Also; the 3.1.4 Prefs/Workbench has a toggle for NewIcons.
Yes, but this does not require a new library for that. Neither did 3.9.
 

Offline H_Celine

Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #161 on: January 25, 2019, 10:31:19 AM »
Reason I am asking is it was not 3rd party in 3.9,
This would surprise me. 3.9 certainly did not include something called "newicon.library". Its icon.library supports "newicons", and so does the 3.1.4.1 version as it is a later version of the 3.9 icon.library.
I admit I have not dug out my original CD, but this is what the iso says:
Code: [Select]
6.AmigaOS3.9:OS-Version3.9/Workbench3.9/Libs> list
aml.library                63768 ----rwed 25-Dec-99 22:13:38
asl.library                58132 ----rwed 18-Nov-00 18:59:04
commodities.library         8460 ----rwed 16-Oct-00 21:18:20
datatypes.library          18752 ----rwed 25-Dec-99 22:00:18
diskfont.library           17200 ----rwed 16-Nov-00 22:25:54
hdwrench.library           37956 ----rwed 26-Nov-00 18:40:32
icon.library               45264 ----rwed 18-Aug-00 15:06:44
locale.library             18088 ----rwed 07-Nov-99 11:58:38
mathieeedoubbas.library     3612 ----rwed 23-Nov-00 22:42:44
mathieeedoubtrans.library    9088 ----rwed 23-Nov-00 22:42:44
mathieeesingtrans.library    6844 ----rwed 23-Nov-00 22:42:44
newicon.library             3588 ----rwed 27-Oct-00 13:09:22
rexxmathlib.library         5760 ----rwed 26-Oct-00 23:28:08
rexxsyslib.library         33404 ----rwed 26-Dec-99 10:45:24
version.library              352 ----rwed 14-Nov-00 15:52:02
vnc.library               123600 ----rwed 25-Nov-00 13:09:44
wizard.library            224240 ----rwed 24-Apr-00 09:53:34
workbench.library         199852 ----rwed 24-Nov-00 09:08:58
xad                          Dir ----rwed 28-Nov-00 11:49:36
xadmaster.library         105332 ----rwed 27-Nov-00 23:15:02
19 files - 1 directory - 513 blocks used
Edit: It also says version 45.0, a version I can not find anywhere else.
« Last Edit: January 25, 2019, 10:33:55 AM by H_Celine »
 

Offline First Ninja

Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #162 on: January 25, 2019, 05:50:54 PM »
Frankly, I don't know. It's some third-party component I don't have and I don't use, and 3.1.4 does not require to operate. It does support more colorful icons out of the box.

Wikipedia establishes that:

Quote
NewIcons are relatively large in file size compared to conventional Amiga icons or MagicWB icons. NewIcons are stored in 8-bit data even when only few colours were used. Image data is encoded in ASCII to application metadata [...]

[...]

The GlowIcons format, based on NewIcons file format, is the native icon format used in AmigaOS 3.5, 3.9 and 4.0 by Matt Chaput. The major difference to NewIcons is how image data is stored. NewIcons uses inefficient ASCII encoding embedded to the application Tool Type metadata. In GlowIcons system developers extended internal icon definition without need to resort to storing information as Tool Types.

Am I right assuming Workbench 3.1.4 can identify, parse and use the RGB color definition/image data encoded as ASCII in the Tool Types meta data (and that, accordingly, Workbench 3.1.4 can use NewIcons icon-files natively)? Does 3.1.4 natively support the GlowIcons extensions, too? Which one of the formats do those extra icons shipped with Release 3.1.4 use?

Offline Thomas Richter

Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #163 on: January 25, 2019, 09:00:44 PM »
Am I right assuming Workbench 3.1.4 can identify, parse and use the RGB color definition/image data encoded as ASCII in the Tool Types meta data (and that, accordingly, Workbench 3.1.4 can use NewIcons icon-files natively)?
Yes, this is correct, provided you enable support for it. It is not its native format, though. If the V45 icon.library wants to store deeper bitmaps, it just writes more bitmaps and indicates its number in the written image structure. The "NewIcons" definition was really only a workaround or a backwards-compatibility hack by the newicons.library for enabling more colorful icons without changing the legacy structure on disk.

Does 3.1.4 natively support the GlowIcons extensions, too? Which one of the formats do those extra icons shipped with Release 3.1.4 use?
I am not quite sure what you refer to as "GlowIcons extension", but given that 3.1.4 ships with a GlowIcons icon set, I would believe the answer should be "yes". (-:

Offline chris

Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #164 on: January 30, 2019, 05:49:08 PM »
Reason I am asking is it was not 3rd party in 3.9, and the codebase in question was originally compiled against that version. And it seems version included with 3.9 does not like 3.1.4(not conclusive, still testing).

Edit: Also; the 3.1.4 Prefs/Workbench has a toggle for NewIcons.

I believe the 3.9 newicon.library was a stub/emulation for programs that used newicon.library directly.  You don't need it unless you have such an old program.
"Miracles we do at once, the impossible takes a little longer" - AJS on Hyperion
Avatar picture is Tabitha by Eric W Schwartz
 
The following users thanked this post: H_Celine