Hi Proteque, another great video. Keep them coming. BITD I never had an HDD for my Amiga, so whenever I tinkered with WB most of my changes were lost. I've got a couple of clean WB installations set up in the emulator that I'm using (FS-UAE) You've actually inspired me to have a go at changing the icon sets, and settings myself ! So thank you very much.
This “you have to press Return to accept the value of the text box” haunted me a lot in the beginning when I went from the Amiga to the PC, where pressing Enter usually accepts the current state and acts like clicking OK. To me, the approach of the Amiga, is still more logical. The best would be a combination of both worlds, incorporating the Tab function to go to the next field - pressing Enter should accept the current value and tab to the next input field, arriving at OK in the end.
Thank you. This video is nice, short and sharp covering many applications. I missed the customisation when I shifted off the Amiga to the PC. Windows eventually caught up but the freedom to change was important to me at the time and the reason I nowadays use Android over iPhone. I also would like to see people's customisations of Workbench. It's just fun. I would like to see how far people with more creative minds than me can customise it.
Ah genialt. Ja, jeg hadde egentlig tenkt å bruke de i videoen, men siden alt var gammelt og glemt i combo med uscripta ombestemte jeg meg undervegs. Tenkte ta en egen video om themes. Ping meg gjerne når du slipper så kan jeg vente til da
You really should put extra user content in the "user-startup sequence" instead of the primary startup-sequence (only edit this for stuff which simply must be there!)
@@proteque There are a couple valid reasons: 1) Startup-sequence are primarily for system and very early startup things. Yes sometimes you have to put user additions in this file due to startup order or timing and such. But if possible it should be avoided due to reason 2. 2) If upgrades or major changes are made to workbench the startup-sequence can be overwritten (partially or completely) But this usually do not apply to the User-startup. It is normally good practice to separate the system stuff from the user stuff. It can also save alot of time and effort. It is good practice to keep the startup-sequence short and simple. Errors in the startup-sequence can bork the system. But errors in User-startup usually only means that some programs or paths do not work (but the system in general still work fine). When starting executable files (or scripts) it is also a good thing to put them inside conditional checks of existance (IF EXISTS...) as a safety net in case the file is missing or having the wrong name or path not being correct (Things can happen..). This way the startup simply skips problems without causing any issues in the general system. It is a bit extra but if system stability is premium (not to mention partition and filesystem safety) then it also good to separate workbench core files (basic installed files plus official updates) from user added files. This is done by having a secondary workbench partition OR a User partition with a Workbench folder in it (which mirrors the folder structure of the core installation). It is then possible to extend the search paths of all major system folders and aliases. This would mean that SYS: has a companion Alias called SYS2: As an example: C: goes both to SYS:C and SYS2:C. These extensions are also put into the User-Startup. They have to be created for each major system path (PATH ADD...) This essentially makes the core installation "immutable" in a sense. This also means you never install anything in SYS:Folder but always direct the installation program to SYS2:folder (the user twin of the workbench) This makes the Workbench extremly hardy and difficult to corrupt in any way. In fact you could even put all files and folders in the core installation as "read only" in order to make it even more rubust. If you then clone the core installation and the User partition separatly into LHZ or LHA archives, then you have a nearly indestructable system. If you at all have to put in things in the startup-sequence but the placement is not critical, it is better to add a another scriptfile with conditional checks of existance (IF EXISTS...). Then you can edit this external scriptfile instead. In this script file you add whatever you want which has to be placed in the startup-sequence. But the general rule should always be: if it is user added it goes into the User-startup.
I have not tested. But I have a hunch they are in the same format but using png so a newer icon.library is all that is needed. I will come back and let you know if I get around to test it. I have 4.1 running so I can grab an icon from there and test.
