@database AmiStart.guide @rem $VER: AmiStart.guide 0.59 (11.02.02) @font courier.font 13 @node MAIN @title "AmiStart Documentation V0.59" AmiStart Documentation read important @{"Notices" link NOTICE} , for example what to change in your old config some general notices @{"First of all / DISCLAIMER" link FIRST} what you can do and what you can't @{" Legal notice / COPYRIGHT " link COPYRIGHT} read the @{" Introduction" link INTRODUCTION} to learn more about it all @{" Requirements " link REQUIREMENTS} you need to use me how to @{" Install " link INSTALLATION} AmiStart what are the @{" Features " link FEATURES} of mine The @{" USAGE " link USAGE} of AmiStart external @{" Modules " link MODULES} Support an @{"AREXX" link AREXX}-interface for external access what @{" Bugs " link BUGS} do i have slow @{" Performance " link PERFORMANCE}? @{" Thanks " link THANKS} to all of you the @{" History " link HISTORY} to see the progress my @{" Last Words " link LASTWORDS}, all i wish to @{" Contact " link CONTACT} me @endnode @node NOTICE "Notice to the using of AmiStart" @{b}NOTICE:@{ub} Important: check the MAPPED ToolType if you have problems This version was compiled for mc68020 and above, i think thats no problem. Since Version 0.56 it is recommended to rise the stack size (16384 bytes for example), this is important because of the recursive removing from directorys (16384 is just a suggestion, i don't know the exact value). The guigfx.library is not longer optional since Version 0.56 uses it for Icon handling. Since 0.59 there is a popup-menu build in (see requirements), this needs the Right-Mousebutton handling to be changed, but thats has nearly no effect, you could close Layers as before by clicking the RMB, but this must be done a very short time, longer pressing down the RMB cause to popup the PopUp menu. Since Version 0.59 MUI is not longer optional, coz i use it for requesters to enable more keyboard shortcodes. In 0.59 some changes are done in the transparency handling, see USAGE/Others WARNING: AmiStart has massive problems on 256 Color wb-views, no idea why Since version 0.59 AmiStart can only be started once, a new call will stop a running AmiStart task @endnode @node FIRST "First of all / DISCLAIMER" @{b}First of all / DISCLAIMER:@{ub} I start this program in 1998, and sold my Amiga 1999, i continued in 2001 on WinUAE, coz Windows programming is arghhh... This Documentation is very BETA, and only a startup Document, i change this if i get user response (or i hope anyone will do this job). I'm not liable for any damages on your Hard and/or Software, it's your risk to use this Application. @endnode @node COPYRIGHT "Copyright" @{b}Copyright:@{ub} This Tool is Freeware, but i ask for an e-mail (address follows below). Note: This is only valid for the AmiStart executable, see the included readme file for copyright informations for the additional content. @endnode @node INTRODUCTION "Introduction" @{b}Introduction:@{ub} As many other Tools this one is an other example of a Windows like Starmenu, unlike most of them you can drag&drop items direct in the menu. At time you can not use Images like jpegs or iffs for the items, you only can use icon files so you should use Newicons or i hope it looks well with the new icon.library in os >= 3.5. Since 0.59 it's possible to use the iconobject.library in the scalos package. Also you can use a Filesystem, which will be displayed. To learn more about the Possibilities of AmiStart read the Usage. @endnode @node REQUIREMENTS "Requirements" @{b}Requirements:@{ub} Hardware: - any Amiga with at least a 68020, without a fpu it crashes here, but i think that's a problem of my System coz i have patched some libs to use the fpu. I have not used any fpu compiler settings. - its recommended to use a gfx-card and a fast system. Software: - wb 3.x - wbstart.library (under OS >=3.5 this should be not needed). - guigfx.library (since 0.56 needed). - MUI (3.8) since (0.59 not longer optional). - If you like to use the PopUp menu, you need to install the popupmenu.library - The commands setup needs the nlist(view) class for mui. - optional the iconobject.library and addons (like datatypes) from the scalos package the "should" means i couldn't test it coz i only own OS 3.1. @endnode @node INSTALLATION "Installation" @{b}Installation:@{ub} only drag the content to the WBStartup directory and/or optionally change the tooltypes (don't replace the prefs file and the additional content if you wish to use the old data). I included a install file in the packages above 0.57, but you can still install as above. The installer file should not overwrite old files by selecting the right options, and you can set the TOOLTYPES automatic. Don't blame me if it won't work, i've never make a install file before. @endnode @node FEATURES "Features" @{b}Features:@{ub} - displays unselected and selected images, - drag & drop - displays filesystems - small arexx port, which enables to add entrys (for example by the installer (like windows)) - changing the prefs file (by external editor or a text editor) causes AmiStart to reload it. - keyboard support (since 0.52) - fully hideable (since 0.53) - texture support (since 0.56) - transparent backgrounds (since 0.58) - direct commodities support (since 0.57) - iconobject.library support (since 0.59) - popupmenu support (since 0.59) - added filesystem action commands (copy/move/delete). (since 0.59) - added external module support (since 0.59) - added the possibility to convert each starticon into a clock. (since 0.59) @endnode @node USAGE "Usage" @{b}Usage:@{ub} Using the word "BUG" in the following description does not should say a dangerous bug, it could be for example a simple visual problem without any crashes. @{b}Tooltypes@{ub}: PREFS=xyz name of the prefs file (must exist). STARTICON=xyz name of the icon file (without .info extension) this icon is used for the start-button, you can click on. CX_HOTKEY=xyz (since 0.52) an optional hotkey to popup/popdown this tool NOBORDER don't border the starticon (icon is not transparent). You could paint your own borders. SILENT (since 0.53) setting this flag makes amistart fully invisible, until you press the hotkey or use the AUTOPOPUP flag described below. AUTOPOPUP (since 0.53) only if SILENT is enabled, makes Amistart visible by moving the mouse in the leftmost bottom edge of the wb-screen. TRANSPARENT (since 0.57) make the Starticon "Transparent", means that the Background color is replaced with the Background. The problem is that this only work properly if no Window is in front of the StartIcon before AmiStart starts, background changes won't be recognized while AmiStart is alive. DATAPATH (since 0.57) set the path for the relativ positioned data in the startup prefs, this were for example icons which are not absolutly located. For example "icons/up.info", with unset DATAPATH this is loaded with the path "progdir:icons/up.info" with DATAPATH the path is "DATAPATH/icons.info". This enables you to leave out the example setting icons out of the wbstartup drawer. Nevertheless these is only a path for the data in the sm.prefs file not for the starticon. NOTOOLTYPES (since 0.58) this disables the Filessystem TOOLTYPE support (see below), could speedup reading filesystems (the first time), but on my Hardware this seems to have no effect in speeding up something. JUMPQUALIFIER=xyz (since 0.58) this ToolType changes the qualifier to jump multiple entries in a Layer by the keyboard mode. Following strings are possible "lalt", "ralt", "ctrl", "lshift", "rshift" (default is left alt). FASTSCALE (since 0.58) in 0.58 the scaling algorithm for small icons was rewritten, this looks better but could be slower and needs more colors, so users without a gfx card should use this Tooltype to force AmiStart to use the old algorithm. USEICONOBJECT (since 0.59) use the scalos icon rendering system, so you can use NewIcons without the Newicon patch. note, it is not required to install scalos but at least the iconobject.library and the datatypes. NOMASK (since 0.59) if you dont like to use backgrounds / transparency you can also set this tooltype to force off the mask generating. This results in less memory usage and should be a bit faster. You can try to use this Tooltype also when you get some visual errors. LATELOAD (since 0.59) by setting this Tooltype AmiStart loads nearly all icons first time if you open a menu, result of this is that AmiStart faster boots up and needs less memory if you don't use all sub-menus. But this delays the first opening of a menu. INFOMODULE=xyz (since 0.59) if you don't like the wb information requester for filesystems, you can specify here a shell module to take this part, for example the scalos information module. MOREUNSHARP (since 0.59) setting this ToolType amistart does more rendering cycles to generate the unsharp transparency background NOMASKCHECK (since 0.59) by default AmiStart checks the mask of the starticon to recognize if the user points over the StartIcon, this could be problematic if the StartIcon is partial transparent. Using NOMASKCHECK lets check AmiStart only if the mousepointer is inside a rectangle about the StartIcon. This ToolType needs the TRANSPARENT ToolType to be set. CLOCK (since 0.59) setting this ToolType the AmiStart start icon will be translated into an analogue clock (note: you MUST use the TRANSPARENT ToolType in the AmiStart icon too, to enable this feature), in this case the clock-pointers will became default parameters but you can still change them by using ToolTypes inside the start icon file. Use following ToolTypes inside the starticon: CLOCK_X = x position of the begining of the pointers, 0 = left CLOCK_Y = y position of the begining of the pointers, 0 = top CLOCK_HOUR_R = r CLOCK_MINUTE_R = r CLOCK_SECOND_R = r length of the pointers in pixels CLOCK_HOUR_COLOR1 = color1 CLOCK_HOUR_COLOR2 = color2 CLOCK_MINUTE_COLOR1 = color1 CLOCK_MINUTE_COLOR2 = color2 CLOCK_SECOND_COLOR1 = color1 CLOCK_SECOND_COLOR2 = color2 colors of the pointers, color1 = color at the start of the Pointer (middle of clock), color2 = color at the end of the pointer. Each color must be entered hex with the following ARGB format 0xaarrggbb, aa = alpha value, rr = red value, gg = green value bb = blue value, all in the range from 0x00 upto 0xff, alpha is not used but should still be set to 0xff. Note: pointers are drawn with nonsystem linedraw, so its possible to make them AntiAliased but they use much more cpu resources. CLOCK_NOSECOND disables the second pointer CLOCK_BIGPOINTER makes the minute and hour pointer a bit widther, so it will be much better visible. i have included a fast painted clock icon, named Clock.info in the icons drawer. STARTDELAY=xyz (since 0.59) delay starting AmiStart, xyz = time in 1/50 secs -> STARTDELAY=50 waits one second before AmiStart starts. This could be usefull, if your workbench has a background and you get a gray background around the starticon using the TRANSPARENT ToolType after you workbench gots its background. Delays also if the wb-screen reopens FORCEREFRESH Normaly AmiStart updates Layers only by resizing them, but some visual updateoperations won't work this way. Using this Flag AmiStart reopens the Layers so for example setting the Transparency flag will be shown immediantly. Note, this is only recommendent on faster systems. (see Bugs). MAPPED There are two possibilities to handle icons, the first is to convert them to the screen resolution (=depth) the other handle always 256 Color Icons. Using MAPPED all icons are converted to 8 Bit depth this should be "much" faster and on non true/hi-color screens needs less memory but could cause problems on some systems. Try MAPPED First if all runs well leave it, else remove this ToolType. @{b}Setting up AmiStart@{ub} To add a Tool, simply drag it's icon on a location in the startmenu. To add a Filesystem, simply drag a Drawer (Filesystem) icon on a location in the Startmenu and select Filesystem To add an Application-Drawer, simply drag a Drawer (Filesystem) icon on a location in the Startmenu and select Application. to change positions of Applications, Drawers ... drag it's Name to the destination location. (dragging from Filesystems to Application-Drawers is possible, other way is not possible, because FileSystem Layers are Temporary) to change the properties of the items, press and hold the left mousebutton down (not move the mice) until the Properties Window appears. (needs MUI) to change the Logo and some default parameters do same as above in the Logo. - the included logo was fast painded with photoshop (i'm not an artist), notice that the logo is painted from bottom upto top without resizing it, if the layer is heigher than the logo the logo is scaled up else it will be truncated. The included logo is in jpeg format this causes a larger amount of time to decode it first time, user with low-end processors could repack it or use an other logo. to remove entrys, drag them out of the windows to save an configuration click exit and then save or configure a new button (application) with the save command or use the arrex command "SAVE" to use background textures, select a pattern-number in the cycle-button (enter the name of the background (drop a image file, or popup the asl-requester)), you can use up to 10 patterns and one empty pattern named "----", this patterns are global so you don't have to enter the pattern-image in other layers to reuse the same pattern only select the same number. To change the pattern of the Start-Layer select the logo an press left-mousebutton a while, to change the pattern of a directory select its root with the left-mousebutton a while. Since 0.58 you can set the pattern cycle button to the "RND" entry, this will take a random pattern from the list edited above. Note all patterns you define, are loaded by startup and stay in memory. To get direct commodities Support, drop a new application on a Layer and select it with the Left-mousebutton a while, then change the Command to Commodities (change the icon files if wished). To change filesystem properties somewhere within the Filesystem tree, set following ToolTypes in the Icon you want to change (needs orgicons flag to be set) for Files/Dirs: AMISTART_SMALL=ON|OFF make this icon small, for Directorys: AMISTART_SMALLCONTENT=ON|OFF make content of this dir small AMISTART_ICONSONLY=ON|OFF show only files with ".icon" extension AMISTART_ORGICONS=ON|OFF show original icons (*) AMISTART_FILESONLY=ON|OFF show only files AMISTART_DIRSONLY=ON|OFF show only directorys AMISTART_NOICONS=ON|OFF do not display the .info files AMISTART_SORT=ON|OFF sort content AMISTART_SORTTYPE=DIRSFIRST|FILESFIRST|MIXED position of dirs and files (*) using the OFF flag switches the support of all AMISTART_xyz properties off in all subdirectories, coz no orgicons were loaded. you can setup a default tool for a filesystem directory, in this case AmiStart starts this Tool with the file or drawer as a parameter. Only directorys can get this ToolType and only a press onto this directory or its file content starts this Tool, not a click on it's drawers, in opposite to the above ToolTypes this not inherit. AMISTART_DEFAULTTOOL=NAME for example you have a Filesystem "Daten:", with the following tree Daten: - Sounds - mp3 - song1.mp3 | | | - wave - song2.wav | - Graphics - iff - background.iff | | | | | - jpg - pic1.jpg | | | |- pic2.gif | |- pic3.gif | |- pic4.gif | - pic5.tiff | | - Others - and you set this tooltype in daten:graphics.info, a click on pic3.gif starts this tool with "pic3.gif" as parameter, a click on the jpg drawer does nothing, you must set this tooltype in daten:graphics/jpg too. But a click on daten:graphics starts the tool with "daten:graphics" as parameter. Note: the root "Daten:" can't have this ToolType set. the NAME parameter should content the path to the default tool, use the tocken {f} as a place holder for the filename of the file you click, dont use {F}, leaving this token does not insert the clicked file/dir. The tool does not run Asyncron so you need to add a "c:run" command infront of the default tool, don't forget the path to the run command!. For Example AMISTART_DEFAULTTOOL=c:run sys:utilities/MysticView {f} AMISTART_DOSPATTERN=pattern to set a matching pattern, only entries with a filename that matches this pattern will be displayed (see your DOS manual). Since 0.59 you can use a popup menu, simply press the right mouse button a bit longer, coz make a short click closes all layers of AmiStart. You can setup commands for files & dirs, to do this open the Commands Settings and add commands, select wb to start the apps like workbench tools. You can change the positions by dragging them. @{b}Keyboard usage (since 0.52)@{ub} - up-arrow: go previous item - down-arrow: go next item - right-arrow: go inside a directory - left-arrow: leave a directory - HOTKEY: only to popup / popdown this tool (no exit!) - lalt(*) +up/down: jump multiple entries up/down - Escape: hide all layer - r: remove entry under cursor - m: show popup menu (*) could be changed through the JUMPQUALIFIER Tooltype @{b}adding a command@{ub} adding a command is equal to add a application to AmiStart, drop a Application! from the Workbench to an AmiStart Layer at a position you like. This adds a default command to AmiStart where default means Execute command. After doing this you can call the setup window and changing the command in the commands cyle tab. Commands are SAVE, QUIT, COMMODITIES, EXECUTE and in V0.59 possibly EXTERNAL @{b}Others@{ub} since Version 0.58 backgrounds could be transparent, check the checkmark to do this, you could set the tint of transparent Layers in the global properties. Layers become only transparent, when enough memory is available otherwise the Fallback pattern will be used. Transparency needs TRUECOLOR screens, but it can work on low-color views too, i don't tested it very much. changings in 0.59: in previous versions checking the Transparent flag disables imaged backgrounds and makes Layers transparent since 0.59 you must select an Empty Background for this or set the Transparent value to 100%, using a image and the Transparency flag the selected background-image will be mixed with the content of the layer-background with a specific ratio (0-100%) and then used. (0% -> only the image will be used, 100% -> only the background of the Layer will be used (= as before), 50% halve/halve) the ratio will only be used if a background image is selected and the transparent flag is enabled. Also the tint will only be used for unimaged-backgrounds. Note: Sometimes changing parameters seems to have no effect, in this try to reopen the layer this should work. to copy/move data from a filesystem to another, first select the sourcepath with "filesystem/copy" go to the destination and select "paste or move". If your source is a drawer you have to select further if you want only to copy the contents or make a drawer named as your sourcedrawer and then copy the contents to this drawer. Copy could be also done by drag&drop a source (filesystem) to a destination layer! to delete data, select it and choose filesystem/delete. note: you first should play with the filesystem commands to get knowledge how they work. Use unimportant data to do this. I'M NOT LIABLE FOR ANY DAMAGES ON YOUR HARD/SOFTWARE USING AMISTART! try out the Parameters! @{b}Parameters that couldn't be setup in the properties:@{ub} you could setup a value for the space between items in a Layer in the prefs file, to do this change the SPACE parameter. you could add a separator bar unter an item by adding the "GROUP" keyword after the NAME parameter in the prefs file @endnode @node MODULES "Modules" @{b}External Modules (since 0.59) @{ub} in Version 0.59 or newer AmiStart handles external modules for Layers, modules could display (screens,windows tasks ...). The AmiStart package includes a sample module called showwindows.module in the ModuleSDK.lha archive, you can get a description of this module after installing it (see below) and choosing it. either copy the xyz.module/info file into the modules directory where AmiStart is installed or in the modules directory inside the DATAPATH defined with the DATAPATH ToolType, or read the doc for this module to learn how to install it. Normaly modules needs icons to display its items, this are normal the module info files distributed with the module. For example a module named showwindows.module should have the icon showwindows.info in the modules directory. after installing a module and restarting AmiStart!!! (note Modules are libraries and therefore resistent, so you need to reboot, or using "avail flush" in the shell before updating a module version), you can setup the module, to do this act like adding all commands to AmiStart, see above. Set the commands cycle bar to external and choose the module in the module list. The config string is described in the module documentation. if AmiStart finds any modules in the modules directory a new command appears in the commands cycle bar, else this point does not appear. @endnode @node AREXX "AREXX" @{b}AREXX:@{ub} AREXX-PORT-NAME: "AMISTART" AREXX-COMMANDS: Commands and Keywords are Case-Sensitive All parameters like values and strings must be quoted by "" [] are optional parameters SAVE save Preferences under the name defined in the tooltypes (defaults to "sm.prefs") ADDITEM NAME="Title" [ICON="info-file"] [DIR="Directory to insert item"] FILE="wb-application" adds an application to the startmenu NAME the title of the Application ICON the icon file FILE the application executable itself DIR where the item should be inserted (not the title of the Directory) without this parameter the application will be inserted in the "ROOT" directory (should be the Programms Directory), if it is not possible in the "MAIN" directory (the directory which pops up by clicking on the start button/HOTKEY). (the "MAIN" directory can not be removed) @endnode @node BUGS "Bugs" @{b}Bugs:@{ub} Caching FileSystems (icons) uses a very simple algorithm, this means the cache would never be cleaned up so it could cost much memory by entering lots of directorys. sometimes amistart doesn't seems to react on keys (don't know why, but thats not a fatal error, in this case move the mouse on an open layer (don't click), so the keyboard support works again). (NOTE: AmiStart needs that it's windows are activated to support keyboard control, tools like MCP could cause errors. (you should not use options like ActivateWindow)) changing various parameters doesn't seem to work properly, this is only while the setup window is alive. Close the setup-window (and all Layers) and all works fine (especialy FileSystems needs to close the Setup-window first). the direct commodities support needs some private (undocumented) functions/structures from the commodities library, there is no guarantee that it'll work on future os versions. transparency needs much memory while layers are alive, further they could be very slow. Using this feature on scrollable layers (Filesystems for example (but Application Directorys are scrollable as well)) is not recommended because this scrolls the background as normal patterns do. NOTE: it isn't possible do do fixed backgrounds. parts of icons could have a bad background. I use the patch NI_RemapFix for NewIcons, i have changed it to work with AmiStart as it works with the wb. Send me a mail if you want to use it, and there is no copyright violation. doing filesystem actions like copy/move delete is your own risk, this functions were not well tested. it could be useful to rise the stack for this commands, coz they use recursivity to go through the filesystem structure. Note using 256 color workbench screens: The following words are for users of 256 color workbenches. I could not confirm if this is a general problem, or if this is only one of my machine using Picasso96. Here it seems that AmiStart won't run correct on 256 Color screens, i cannot figure out why this happen but it only appears on 256 color views not on 128 or less. There is nothing in AS which has the effect to act so, but on 256 color views something starts to remap pens while AS is running, this happen independent if you use AGA or a GFX-Card. Note for users of the USEICONOBJECT ToolType (Scalos users): There is a masking problem by using AS with AGA workbenches, thats not a crash problem. So you don't should use AS with iconobject datatypes(libraries) on AGA wb-screens. I Think this should not be a problem, coz AGA is outdated. Using the FORCEREFRESH ToolType gives no guarentee that the redrawn Layers are displayed correct under any circumstances. This is not ever valid if more layers are opened, coz for especially Transparency AmiStart needs to read the background before opening a Layer, Layers are redrawn from left to right, so if a Layer in a more left position will be redrawn a bit false if its contentpane grows. more weighty are not known yet. send me an mail if you find more, in this case note your configuration: - your os version - are you using workbench replacement tools (dopus/scalos) - processor (if < 020, i compiled AmiStart for 020 and above) - do you use a gfx-card or the old chipset, (most things in amistart are optimized for true-color, it must run on aga/ecs but if there are graphical trash on your non-true/hi-color screen i propably never fix this, coz aga/ecs is outdated). - patches Note: If you have graphical trash (f.e. icons are bad or not displayed, try first the NOMASK ToolType, and mail me the result of this try. Note: AmiStart isn't a low-config-computer-application. @endnode @node PERFORMANCE "Performance" @{b}Performance:@{ub} loading different icons is very slow, so you should decide to use default icons for filesystems, which contains masses of entries this also consumes much less of memory, because this icons are only loaded one time instead of loading each icon by using ORGICONS. So projectdata like images/music should be loaded through AMISTART_DEFAULTTOOL instead by for example (deficons) DEFAULTOOL. @endnode @node THANKS "Thanks" @{b}Thanks:@{ub} special thanks must go to (order of appearance is random and does not say anything): Martin Mason Merz for the beautiful Artwork. Emiliano Esposito for the italiano catalog. Nicolaos Damilakis very lot of ideas and the greek catalog. Richard Kapp (GfxBase) for ideas and nice ideas. John Wasilewski for Beta-testing. Nicholaus Darley Jones for Beta-testing. (TLT) Lee for Beta-testing. Luca (Hexaae) Longone for Beta-testing and to be the first user who sends me an e-mail. Andreas R. Kleinert for his sample Library code used for the ModuleSDK thanks for your ideas. @endnode @node HISTORY "History" @{b}History:@{ub} changes since: Version 0.58: - spaces in the prefs could be negative now. - AmiStart is only launchable once now, a second launch will stop AmiStart - added CLOCK ToolType - screennotify again rewritten (should now work) - added some filesystem action like copy move and delete complete filesystems (see bugs). - changed all requesters to use MUI, so they can be controlled by keys - fixed default-icon path bug (paths must be absolute before) - added LATELOAD ToolType - added NOMASK ToolType - added USEICONOBJECT ToolType, (usefull for scalos users, see bugs). - added popupmenu.library support - fixed non-gfx-card BUG - fixed a color bug, so titles are displayed with the selected color - added INFOMODULE ToolType - added external module support (section Modules) - added MOREUNSHARP ToolType - added NOMASKCHECK ToolType - added STARTDELAY ToolType - added FORCEREFRESH ToolType - transparency in layers also includes Background images - added MAPPED ToolType (very important) Version 0.57: - doc type changed to amigaguide format - added a empty background hook, layers wouldn't be erased anymore before a background is painted, this is a bit faster and Layers doesn't flicker so much if they appear. - added FASTSCALE Tooltype - added JUMPQUALIFIER Tooltype - added NOTOOLTYPES Tooltype - use my own scaling algorithm, small images looks now much nicer than the old (guigfx) scaling - added transparency support for Layers - leaving the properties, not longer causes Layers to be closed (see BUGS) - added a french catalog, done by Eric LUCZYSZYN. - added a italian catalog, done by Emiliano Esposito - added a installation script (hope it runs) - AmiStart now reads the DEFAULTTOOL parameter in the Project icons, so you can now use deficons to do acions on data files without icons. (jpegs for example) - pattern could be now changed randomly. - you can use a matching pattern in filesystems. - added AMISTART_DOSPATTERN properties TOOLTYPE for filesystems Version 0.56 - added ToolType DATAPATH, to enable loading data from other locations - on >=3.5 Systems wbstart.lib should not be longer needed, clicking on a Directory inside a Filesystem should open this drawer on the WB screen. - pressing the left mousebutton over a Filesystem item should open the System info-requester for ToolType editing (see bugs). - filesystem settings can be changed somewhere inside the directory structure, so you not longer are fixed to use global filesystem settings - you can set up a default tool for a filesystem drawer - using alt keys with cursorup/down scrolls multiple entries in keyboard mode. - screennotify.library reworked, neverthenlass i cant make it work as it should. - new Command COMMODITIES, so Commodities could be handled now direct by AmiStart - Sorting the Filesystem contents. - Escape Key to hide all layers - Temporary TRANSPARENT Tooltype (makes only the StartIcon Transparent, beware this has some restrictions you will see) Version 0.55 - changing the properties layout - adding "small FileSystem content" flag in the FileSystem properties, this let the Icons be halvesized independent from the root icon. - adding a simple caching mechanism for filesystems, visiting same directorys a 2nd time is now much faster now - changing the Start-icon bordering from double to single border. - addign NOBORDER ToolType, to get the StartIcon unbordered - added FileSystems now uses the right icon file (disk.info) by default - most actions not causes AmiStart to close all layers anymore (delete, add, drag&drop) only changing setting does. - removing of unempty directorys (please rise stack size in the AmiStart icon) - adding Background Support - changing Icon Handling (needs to be done to make icons Transparent on Backgrounds) - titles could be shadowed now. Version 0.54 - color of titles could be changed (value could be different by selected colors). - show only files with icons should now run correct. - using Memory-pools for strings and structures inside the code, this prevents memory fragmentation. - adding support for the icon.library version 44, so AmiStart should now run correct with OS3.5/3.9 - directorypopup disapears by doubleclick Version 0.53 - fixed some bugs (in previous versions dropping same drawers as application drawers causes, that all this drawers contains the same data) - scrolling should cause no layout errors anymore - screennotify handling rewritten, (on std. workbench it seems to run ok, but on dopus i notice problems but it seems that the screennotify.library is faulty because the same error apears on the demo prog on my computer) - added a german catalog and a catalog description file Version 0.52 (not released) - added hidden mode (see Tooltypes description) Version 0.51 (not released) - added keyboard support - removing some little bugs Version 0.5 (first released) - drag&drop handling in now more tolerant - small icons are displayed now correct - mui setup is now working by droping items on the gadgets correctly (before you need to press return in the strings) - arrow space is now added only if arrows are needed - removing items now causes a confirm requester - arrows are now updated correctly - changing the font recalculates all layers (leave the prefs for correct display) - changing flags in the setup works now correct - you not longer need to select an item before clicking on the logo to setup default values - adding LOADALWAYS (reload icon everytime) flag, icons with this flag set are loaded/reloaded everytime the directory appears, so they are load first if you select a directory (like all icons in a filesystem) @endnode @node LASTWORDS "Last words" @{b}Last Words:@{ub} coz AmiStart is a (new) application there is no icon available for it, so if you could do it (the icon itself and one for the starticon) in the great glow-icon style, it would be nice to send me them. Better you make a clockable starticon. @endnode @node CONTACT "Contact" @{b}Contact:@{ub} Darius Brewka d.brewka@freenet.de @endnode