@DATABASE PowerWindows @WIDTH 76 @AUTHOR Georg Steger @TOC "Main" @NODE "Main" "PowerWindows V0.9.1 (C) Copyright 1997 by Georg Steger" @{B} ################## ################### #### ## # # ## # ##### ### ## # #### ### ## ## ## ### ## ## ## ## ## ## ## ## #### ## ## ## ## ###### ## ## ## ## ## ## ## ### ########### ## ## ## ## ## ### ## ## ## ## ## ## ## ## ########### ###### ## ## ## ##### ### ###### #### #### ### ####### ## ## ####### #### ### ######## ### ### ### ### ####### ### ### ### ### ### ####### ####### ### ### ### ### ## ### ### ### ### ######## ### ### ### ### ### ### ### ####### ######### ###### ### V 0.9.1 @{UB} @{" Introduction " LINK "Introduction"} @{" Requirements " LINK "Requirements"} @{" Legal Stuff " LINK "LegalStuff"} @{" Installation " LINK "Installation"} @{" Configuration " LINK "Configuration"} @{" Technical/Bugs " LINK "TechnicalInfo"} @{" History " LINK "History"} @{" Future " LINK "Future"} @{" Author " LINK "Author"} @{" Other Stuff " LINK "OtherStuff"} @ENDNODE @NODE "Introduction" "Introduction" @TOC "Main" - @{I}Some thought it is impossible to do ...@{UI} That's wrong, it @{B}WAS@{UB} impossible to do! - @{I}Some dreamt of it ...@{UI} Most did not even do that! - @{I}It was the most wanted utility of the Amiga-World ...@{UI} and here it is! Let's get ready for @{B}PowerWindows V 0.9.1@{UB} @{B}ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ@{UB} @{U}@{FG SHINE} @{UU}@{FG TEXT} ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ PowerWindows is a little utility, that allows you to move windows out of the Screen. With this program that patches some System-Functions you will finally know where to move your windows when you have opened a lot of them. PowerWindows is especially useful for those of us who don't have a GFX- Board (like me). With the Screen-Resolutions the ECS/AGA-Chipset offers, after having opened two or three Windows you already have to start sizing and moving the windows to get to the desired one. Well, that's over now. With PowerWindows you simply move the windows you actually don't need out of the Screen. With @{FG SHINE}V 0.9@{FG TEXT} all your Windows will also get an Iconify-Gadget. @{FG SHINE}@{B}Read the documentation VERY carefully because PowerWindows installs some very dangerous Patches and you have to configure it correctly before using!@{UB}@{FG TEXT} My English is terrible. Hope you have a lot of fun with it. @{B}PowerWindows is SHAREWARRE!@{UB} @ENDNODE @NODE "Requirements" "Requirements" @TOC "Main" PowerWindows should run on any machine with Amiga OS 2 or higher. I do not know whether it works with GFX-Boards. @{FG SHINE}@{U}PowerWindows was developped on:@{UU}@{FG TEXT} AMIGA 1200 Kickstart 3.0 Workbench 3.0 CPU 68030-50 FPU 68882-50 (Blizzard 1230/IV) 2 MB CHIP / 8 MB FAST HITACHI 340 MB HD WEARNES CD 120-A DOUBLE-SPEED CD-ROM TRUST COMMUNICATOR 14K4 - MODEM @{B}Note:@{UB} This is the only machine PowerWindows has been tested on! @ENDNODE @NODE "LegalStuff" "Legal Stuff" @TOC "Main" @{B}@{U}PowerWindows is Shareware!!!@{UB}@{UU} If you use it more than once a week you must send me: 7,5 DM (5 US $) (5.000 Lire) : If you @{U}like@{UU} it 15 DM (10 US $) (10.000 Lire): If you @{U}love@{UU} it 30 DM (20 US $) (20.000 Lire): If you think it's the @{U}best and most@{UU} @{U}useful utility@{UU} ever created. If you do not it's very unlikely that I continue development. @{U}Send everything to:@{UU} Georg Steger Hochlercher 30 I-39030 St. Johann/Ahrntal @{B}ITALY@{UB} EMail: steger@pass.dnet.it @{B}Important:@{UB} PowerWindows has not been tested very much. Test it for a while and send me Bug Reports. @{U}Copyright@{UU} PowerWindows is written and copyright İ 1996 by Georg Steger. No parts of this program may be altered by any means (this includes editing, reprogramming, crunching, resourceing etc.), except archiving. @{U}Disclaimer@{UU} The author is in no way liable for any changes made to any part of the program, or consequences thereof as he is in no way liable for damages or loss of data directly or indirectly caused by this software. @{U}Distribution@{UU} Neither fees may be charged nor profits may be made by distributing this piece of software. Only a nominal fee for costs of magnetic media may be accepted, the amount of US $5 shouldn't be exceeded for a disk containing PowerWindows. CD Manufactures are specifically granted the right to include this program on CD collections, as long as they are for the Public Domain. I would be very nice if they sent me a copy of the CD. @ENDNODE @NODE "Installation" "Installation" @TOC "Main" PowerWindows installs some very critical Patches so it has to be started at the right time. Before installing it you should try whether it works on you configuration. To do this simply launch it from the Workbench or Shell. - As a first test, open a window and move it out of the Screen at the right. @{B}Important:@{UB} You can move the Windows out of the Screen only at the @{B}right@{UB} or at the @{B}bottom@{UB}. This is because the Operating System doesn't seem to like negative Coordinates. - Check whether at the left side of the Screens the part of the Window which should be out of the Screen appears in false Colors. If it doesn't you are O.K.! - Open another Window and move it out of the Screen as well. Check again whether there is no graphical trash at the left side of the Screen. - Now move the Windows to front and to back, close them and always repeat the check. - If the display is trashed remove all patches installed on your System and try again. @{B}Note:@{UB} - It is less dangerous to move Windows out of the Screen at the right be- cause the only thing that can happen is a destroyed display at the left side. (Exception: If the Window's TopEdge+Height=Screenheight then it is also possible that foreign memory is trashed!) - Moving Windows out of the Screen at the bottom is more dangerous. - If you don't see trashes when you move Windows out of the Screen at the right then moving it out of the Screen at the bottom will work, too. - Make a lot of tests before installing it (with ALL your programs). I must repeat, this is a very dangerous program. - In order to move the Windows out of the Screen, PowerWindows has to change the Screen's Width and Height for a short period of time to 16383. This period is the most critical. @{FG SHINE}- @{" Configure " LINK "Configuration"} PowerWindows to avoid Programs that draw to the Screen-Rastport directly (like Deluxe Paint IV). Such programs will al- most certainly cause Crashes.@{FG TEXT} - Again, do a lot of tests and watch out for Crashes. Moving Windows out of the Screen at the bottom WILL NOT trash the Screen but MAY overwrite foreign memory! - Remember. This is only Version 0.9.1!!! Expect some bugs and crashes! - Don't force the Workbench-Screen to be closed/opened in critical si- tuations, this is when a program is going to close/open a Window on it. - It is possible to quit Powerwindows by sending it a CTRL_C (in non- critical situations). @{U}Anyway you should not quit it.@{UU} @{B}Installing it:@{UB} For now you have to install it by hand. You can start it in the Startup- Sequence, in the User-Startup or even in the WBStartup. It SHOULD be started very lately in order to be the last program to patch layers.library, al- though it depends on the patches and programs you have installed on your Computer. You have to try it out. If you want to start it in the User- Startup or Startup-Sequence use "run <>NIL: PowerWindows" - PowerWindows MUST be started AFTER programs that @{U}replace@{UU} Layer-Functions completely in order to speed up things. - MCP (Master Control Program) seems to be buggy. You should not use Power- Windows when MCP is active. - MagicLayers works, but you can't move windows out of the Screen with it and you have to set a Qualifier for Out-Of-Screen-Draggings. If you do not set a Qualifier one of the two programs won't get any change to be active (PowerWindows and MagicLayers both install an Input-Handler with Priority 51). This depends on which program was started first. Anyway with @{FG SHINE}V 0.9@{FG TEXT} you can change the Priority of PowerWindows' Input- Handler in the Configuration File. @ENDNODE @NODE "Configuration" "Configuration" @TOC "Main" To configure PowerWindows you have to edit @{FG SHINE}PowerWindows.config@{FG TEXT}. PowerWindows will look for this file in the current directory and in "S:". @{B}Note:@{UB} - Lines starting with ";" or "*" are comments - You can have blank lines - Space-Characters are ignored (but don't add them at the start of a line!) - Syntax : @{FG SHINE}KEYWORD=VALUE@{FG TEXT} for "Specify-Keywords" @{FG SHINE}KEYWORD@{FG TEXT} for "Activate-Keywords" @{FG SHINE}___________________________________________________________________________@{FG TEXT} ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ @{FG SHINE}SCANSCREENS@{FG TEXT} : () Default: OFF If active PowerWindows scans ALL already opened Screens and patches them to allow Out-Of-Screen Movings. @{U}The Tasks@{UU} @{U}(well, its Screens) you don't want to be patched (the ones@{UU} @{U}you have specified with @{FG SHINE}TASK@{FG TEXT}) will be patched, too.@{UU} This is because PowerWindows does not know who's the owner of the already open Screens. @{FG SHINE}TASKSONLY@{FG TEXT} : () Default: OFF If active the Screens opened by Tasks specified with @{FG SHINE}TASK@{FG TEXT} will be the only ones to be patched. By default the Screens opened by Tasks specified with @{FG SHINE}TASK@{FG TEXT} are the ones NOT to be patched!! @{FG SHINE}TASK@{FG TEXT} : (..) Default: With @{FG SHINE}TASK@{FG TEXT} you can specify the Tasks whose Screens you DO want to be patched (if @{FG SHINE}TASKSONLY@{FG TEXT} is active) or the Tasks whose Screens you DO NOT want to be patched (if @{FG SHINE}TASKSONLY@{FG TEXT} is inactive). Programs that write directly to the Screen- RastPort should (it depends on when and how they do it) be stated not to be patched. @{B}Notes:@{UB} - You can specify a Pattern (For Example: #?dpaint#?) - The Workbench-Screen is opened by "#?IPrefs#?" - This Keyword can be used more than once. For example: @{FG SHINE}TASK@{FG TEXT}=#?Workbench#? @{FG SHINE}TASK@{FG TEXT}=#?dpaint#? @{FG SHINE}TASK@{FG TEXT}=visage @{FG SHINE}CASESENSITIVE@{FG TEXT} : () Default: OFF If active Pattern-Matching (for checking if the actual Task that is going to open a Screen is one of those specified with @{FG SHINE}TASK@{FG TEXT}) is case sensitive. @{B}Important:@{UB} You MUST specify this if you have a DOS-Version lower than 36.147 @{FG SHINE}MARKER@{FG TEXT} : (OFF|GADGET|NORMAL) Default: NORMAL - OFF : No marker when dragging windows. Prevents Dead- Locks. - GADGET: The marker gets the coordinates of the Drag- Gadget. - NORMAL: The marker gets the coordinates of the Window. Just like Intuition does. @{FG SHINE}ALLPLANES@{FG TEXT} : () Default: OFF If active the marker renders to all planes. By default it just renders to Plane 1 to speed things up. If you have a GFX-Board you might have to activate this! @{FG SHINE}NORMALQUALIFIER@{FG TEXT}: (..) Default: Qualifier that must be pressed to allow Out-Of-Screen Movings. Multiple Qualifiers must be separated by a "+". @{U}Possible Qualifiers:@{UU} LSHIFT,RSHIFT,SHIFT CAPSLOCK,CONTROL, LALT,RALT,ALT, LCOMMAND,RCOMMAND,COMMAND, You can also specify "NONE" or "OFF" which means, that no Qualifier needs to be pressed. Look at @{FG SHINE}NORMALBUTTON@{FG TEXT} which is new in V 0.9! @{U}Note:@{UU} SHIFT means BOTH Shift-Keys must be pressed, ALT means BOTH Alt-Keys must be pressed, COMMAND means BOTH Command-Keys must be pressed! @{FG SHINE}FORCEQUALIFIER@{FG TEXT} : (..) Default: LSHIFT+LALT Qualifier that must be pressed to allow Out-Of-Screen- Movings. With this Qualifier you can click anywhere in the Window to drag it. Multiple Qualifiers must be sepa- rated by a "+". @{U}Possible Qualifiers:@{UU} LSHIFT,RSHIFT,SHIFT CAPSLOCK,CONTROL, LALT,RALT,ALT, LCOMMAND,RCOMMAND,COMMAND, You can also specify "NONE" or "OFF" which means, that no Qualifier needs to be pressed. Look at @{FG SHINE}FORCEBUTTON@{FG TEXT} which is new in V 0.9! @{U}Note:@{UU} SHIFT means BOTH Shift-Keys must be pressed, ALT means BOTH Alt-Keys must be pressed, COMMAND means BOTH Command-Keys must be pressed! @{FG SHINE}___________________________________________________________________________@{FG TEXT} ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ New Keywords in V 0. 9 @{FG SHINE}___________________________________________________________________________@{FG TEXT} ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ @{FG SHINE}INPUTPRI@{FG TEXT} : (-128 .. 127) Default: 51 This Keyword allows you to specify the Priority of the Input-Handler created by PowerWindows. It should be higher than the Priority of Intuition's Input-Handler which is 50! @{FG SHINE}DEADLOCK_SEC@{FG TEXT} : (0 .. 100) Default: 1 PowerWindows' SubTask checks every @{FG SHINE}DEADLOCK_SEC @{FG TEXT}Seconds + @{FG SHINE}DEADLOCK_MIC@{FG TEXT} Micro-Seconds if a Deadlock has occured. @{FG SHINE}DEADLOCK_MIC@{FG TEXT} : (0 .. 1,000,000) Default: 0 PowerWindows' SubTask checks every @{FG SHINE}DEADLOCK_SEC@{FG TEXT} Seconds + @{FG SHINE}DEADLOCK_MIC@{FG TEXT} Micro-Seconds if a Deadlock has occured. A Second = 1,000,000 Micro-Seconds! @{FG SHINE}DEADLOCK_PRI@{FG TEXT} : (-128 .. 127) Default: 0 Specifies the Task-Priority of PowerWindows' DeadLock- hunting Sub-Task. @{FG SHINE}MAXSPPERIOD@{FG TEXT} : (0 .. 1000) Default: 20 When moving a Window out of Screen, PowerWindows changes the Screen's Dimension to 16383 * 16383. After that it waits until the Window has really arrived at the new Position. When this has happened it resets the Width and Height-Entries of the Screen-Structure to their original values. For some reasons it might happen that the Window never arrives at the new Position, so after the @{FG SHINE}"Maximum Screen Patch Period"@{FG TEXT} PowerWindows resets the Screen's Dimension anyway. The value you specify here is in 10th of a second!! @{B}Note:@{UB} During the @{FG SHINE}"Screen Patch Period"@{FG TEXT} you cannot move the Mouse-Pointer or use the Keyboard. @{FG SHINE}NOMOUSEFREEZE@{FG TEXT} : () Default: Off By default, PowerWindows kills MouseMove-Events while moving a Window. If you don't want that specify this option. If @{FG SHINE}NOMOUSEFREEZE@{FG TEXT} is ON it might happen that the Screen scrolls out of it's limits (because of PowerWindows changing it's Size while moving a Window). In such a case you will see appearing the left part of the Screen in False Colors. If this happens increase @{FG SHINE}MOUSEFACTOR@{FG TEXT}! @{FG SHINE}MOUSEFACTOR@{FG TEXT} : (1..100) Default: 4 If @{FG SHINE}NOMOUSEFREEZE@{FG TEXT} is ON PowerWindows does not freeze Mouse- Movements while moving a Window, but tries to not let the Mouse-Pointer reach any of the Screen's (visible) Borders which usually leads to Auto-Scrolling. As PowerWindows does not know what Intuition/Commodities/other Input- Handlers do with the Mouse-Events (with which factor they multiply the relative Coordinates in the Event-Structure) it might be necessary to increase the value by which PowerWindows multiplies for (checking reasons). @{FG SHINE}ICONIFYGADGET@{FG TEXT} : () Default: OFF If you want to have an Iconify-Gadget in your Windows, specify this Keyword. Only Windows that are opened on a patched Screen will get an Iconify-Gadget. If you want certain programs not to get Iconify-Gadgets for its' Win- dows look at the Keywords: @{FG SHINE}ICONIFYTASK@{FG TEXT} @{FG SHINE}ICONIFYTASKSONLY@{FG TEXT} @{FG SHINE}ICONIFYCASESENSITIVE@{FG TEXT} By pressing the Iconify-Gadget the Window will move out of Screen and on it's Position an Icon (no real Icon, but a little Window) will appear. By clicking this Icon twice the Window will reappear on it's old Position and the Icon will disappear. @{FG SHINE}IGLOOK@{FG TEXT} : (..) Default: NORMAL The Iconify-Gadget can have different looks. The available ones are: @{I}NORMAL@{UI} : The gadget will look like the ones in MUI. @{I}NICE@{UI} : Custom-Look designed by me. (Very nice!) @{I}SYSI@{UI} : SysiHack-Version of "NORMAL" @{I}SYSINICE@{UI}: SysiHack-Version of "NICE" @{FG SHINE}NOICONS@{FG TEXT} : () Default: OFF If you specify this, iconified Windows will NOT be re- placed by an Icon. Has only sense, if you specify a @{FG SHINE}ICONIFYOFFSET@{FG TEXT} > 0; @{FG SHINE}DONTICONIFYWB@{FG TEXT} : () Default: OFF If you don't want Workbench-Windows (WFLG_WBENCHWINDOW) to get an Iconify-Gadget set this in the Config-File. @{FG SHINE}MINWINWIDTH@{FG TEXT} : (0.. 2000) Default: 50 In order to get an Iconify-Gadget Windows must be at least @{FG SHINE}MINWINWIDTH@{FG TEXT} Pixels wide. Windows that have a Size-Gadget are not taken into consideration by this Check. @{FG SHINE}ICONPOS@{FG TEXT} : (..) Default: AUTO_BOTTOMLEFT With @{FG SHINE}ICONPOS@{FG TEXT} you can select on which Position you want the Icons appear. These are the possibilites: @{i}UPPERLEFT@{ui} : The Icon will appear in the upperleft edge of the Window you have iconified. @{i}UPPERRIGHT@{ui} : The Icon will appear in the upperright edge of the Window. @{i}LOWERLEFT@{ui} : The Icon will appear in the lowerleft edge of the Window. @{i}LOWERRIGHT@{ui} : The Icon will appear in the lowerright edge of the Window. @{i}CENTER@{ui} : The Icon will appear in the center of the Window. There are also some amazing Auto-Positioning-Possibilities: @{I}AUTO_BOTTOMLEFT@{UI} : +-----------------+ | | | | | | | | |@{BG SHINE}[ ]@{BG BACKGROUND} @{BG SHINE}[ ]@{BG BACKGROUND} @{BG SHINE}[ ]@{BG BACKGROUND} | +-----------------+ @{I}AUTO_BOTTOMRIGHT@{UI}: +-----------------+ | | | | | | | | | @{BG SHINE}[ ]@{BG BACKGROUND} @{BG SHINE}[ ]@{BG BACKGROUND} @{BG SHINE}[ ]@{BG BACKGROUND}| +-----------------+ @{I}AUTO_TOPLEFT@{UI} : +-----------------+ |@{BG SHINE}[ ]@{BG BACKGROUND} @{BG SHINE}[ ]@{BG BACKGROUND} @{BG SHINE}[ ]@{BG BACKGROUND} | | | | | | | | | +-----------------+ @{I}AUTO_TOPRIGHT@{UI} : +-----------------+ | @{BG SHINE}[ ]@{BG BACKGROUND} @{BG SHINE}[ ]@{BG BACKGROUND} @{BG SHINE}[ ]@{BG BACKGROUND} | | | | | | | | | +-----------------+ @{I}AUTO_LEFTTOP@{UI} : +-----------------+ |@{BG SHINE}[ ]@{BG BACKGROUND} | |@{BG SHINE}[ ]@{BG BACKGROUND} | |@{BG SHINE}[ ]@{BG BACKGROUND} | | | | | +-----------------+ @{I}AUTO_LEFTBOTTOM@{UI} : +-----------------+ | | | | |@{BG SHINE}[ ]@{BG BACKGROUND} | |@{BG SHINE}[ ]@{BG BACKGROUND} | |@{BG SHINE}[ ]@{BG BACKGROUND} | +-----------------+ @{I}AUTO_RIGHTTOP@{UI} : +-----------------+ | @{BG SHINE}[ ]@{BG BACKGROUND}| | @{BG SHINE}[ ]@{BG BACKGROUND}| | @{BG SHINE}[ ]@{BG BACKGROUND}| | | | | +-----------------+ @{I}AUTO_RIGHTBOTTOM@{UI}: +-----------------+ | | | | | @{BG SHINE}[ ]@{BG BACKGROUND}| | @{BG SHINE}[ ]@{BG BACKGROUND}| | @{BG SHINE}[ ]@{BG BACKGROUND}| +-----------------+ @{FG SHINE}ICONPOS_OFFY@{FG TEXT} : (-2000 .. 2000) Default: 0 When @{FG SHINE}ICONPOS@{FG TEXT} is @{FG SHINE}AUTO_???@{FG TEXT} you can set an Offset to add to the calculated Position of the Icon. For example, if you want the Icons to be placed at the bottom of the Screen, but there is also a Toolmanager-Dock there, you can set @{FG SHINE}ICONPOS_OFFY@{FG TEXT} to approximately -40! @{FG SHINE}ICONPOS_OFFX@{FG TEXT} : (-2000 .. 2000) Default: 0 Just like @{FG SHINE}ICONPOS_OFFY@{FG TEXT}, but for the X-Postion. @{FG SHINE}ICONWIDTH@{FG TEXT} : (..) Default: 1/6 @{FG SHINE}ICONWIDTH@{FG TEXT} sets the Width of the Icons. There are several possibilities to get the desired Dimension: - A single value indicates the Width in Pixels: ;We want the Icons'Width to be 100 Pixels! ; @{FG SHINE}ICONWIDTH@{FG TEXT} = 100 - Two values separated by a "/" means that you want the Icons' Width in some way be relative to their Screen's Width: ;If we want the Icon's Width to be half the Screen- ;Width we use: @{FG SHINE}ICONWIDTH@{FG TEXT} = 1/2 ;If we want the Icons' Width to be ScreenWidth*5/31 ;we use: @{FG SHINE}ICONWIDTH@{FG TEXT} = 5/31 - WINWIDTH means that the Icon will have the same Width as the Window. ;The Icon's Width shall be equal to the Window's ;Width: @{FG SHINE}ICONWIDTH@{FG TEXT} = WinWidth - "WINWIDTH / x" means that the Icon's Width will be Window-Width / x: ;We want the Icons' Width to be half the Width of ;their Windows: @{FG SHINE}ICONWIDTH@{FG TEXT} = WinWidth / 2 @{FG SHINE}MINICONWIDTH@{FG TEXT} : (0..2000) Default: 100 By default the Icons get the Width according to what is specified with @{FG SHINE}ICONWIDTH@{FG TEXT}. Nevertheless their minimum Width will always be @{FG SHINE}MINICONWIDTH@{FG TEXT}. @{FG SHINE}ICONIFYTASKSONLY@{FG TEXT}: () Default: OFF If active the Windows opened by Tasks specified with @{FG SHINE}ICONIFYTASK @{FG TEXT}will be the only ones to get an Iconify- Gadget. By default the Windows opened by Tasks specified with @{FG SHINE}ICONIFYTASK @{FG TEXT}are the ones NOT get an Iconify-Task. @{FG SHINE}ICONIFYTASK@{FG TEXT} : (..) Default: With @{FG SHINE}ICONIFYTASK@{FG TEXT} you can specify the Tasks whose Windows you want to get an Iconify-Gadget (if @{FG SHINE}ICONIFYTASKSONLY@{FG TEXT} is active) or the Tasks whose Windows you DO NOT want to get an Iconify-Gadget (if @{FG SHINE}ICONIFYTASKSONLY@{FG TEXT} is inactive). @{B}Notes:@{UB} - You can specify a Pattern (For Example: #?dpaint#?) - Only Windows that are opened on a patched Screen can get an Iconify-Gadget - This Keyword can be used more than once. For example: @{FG SHINE}ICONIFYTASK@{FG TEXT}=PPaint @{FG SHINE}ICONIFYTASK@{FG TEXT}=#?dpaint#? @{FG SHINE}ICONIFYTASK@{FG TEXT}=#?visage @{FG SHINE}ICONIFYCASESENSITIVE@{FG TEXT}: () Default: OFF If active Pattern-Matching (for checking if the actual Task is one of those specified with @{FG SHINE}ICONIFYTASK@{FG TEXT}) is case sensitive. @{B}Important:@{UB} You MUST specify this if you have a DOS-Version lower than 36.147 @{FG SHINE}ICONIFYOFFSET@{FG TEXT} : (0 .. 1000) Default: 0 When you iconify a Window, PowerWindows moves it to the Position (@{FG SHINE}ScreenWidth@{FG TEXT} - @{FG SHINE}IconifyOffset@{FG TEXT},@{FG SHINE}WindowTop@{FG TEXT}). By default @{FG SHINE}ICONIFYOFFSET @{FG TEXT}is 0. In this case the Window will be completely invisible. If you specify a value > 1 you will still be able to reach (and see a part of) the Window and drag it using the @{FG SHINE}FORCEQUALIFIER@{FG TEXT}. @{FG SHINE}SAFEMOVEWINDOW@{FG TEXT} : () Default: OFF By default, PowerWindows calls MoveWindow() in it's Input- Handler. One should not do that (call Intuition-Functions in an Input-Handler) usually. But as MoveWindow() seems only sending a Request to Intuition, it should not be that critical. Anyway if you get a lot of Deadlocks or even Crashes you can try specifying @{FG SHINE}SAFEMOVEWINDOW@{FG TEXT}. If active, PowerWindow's Input-Handler sends a Message to the PowerWindow's Task asking it to move the Window for it. The Window will be moved only after a short delay which might be annoying. @{FG SHINE}SAFELOCKLAYER@{FG TEXT} : () Default: OFF As there is no AttemptLockLayers(), PowerWindows' Input- Handler before locking the Layers has to check if the LockLayers-Call will succeed, otherwise there might be a DeadLock. This can actually be done in two ways, but both are not really System-conform as they rely on System-private Structure-Fields. @{FG SHINE}SAFELOCKLAYER @{FG TEXT}uses the better way (at least I think so). If you get a lot of Deadlocks when trying to move a Window try specifying this. @{FG SHINE}NORMALBUTTON@{FG TEXT} : (LEFT,RIGHT,MIDDLE) Default: LEFT Here you can specify which Mouse-Button must be pressed together with @{FG SHINE}NORMALQUALIFIER @{FG TEXT}to allow dragging the Window out of Screen when clicking on a Drag-Gadget. @{FG SHINE}FORCEBUTTON@{FG TEXT} : (LEFT,RIGHT,MIDDLE) Default: LEFT Here you can specify which Mouse-Button must be pressed together with @{FG SHINE}FORCEQUALIFIER @{FG TEXT}to allow dragging the Window out of Screen when clicking anywhere in the Window. @{FG SHINE}___________________________________________________________________________@{FG TEXT} ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ @{B}P.S.:@{UB} PowerWindows does not patch Tasks, it patches Screens! @ENDNODE @NODE "TechnicalInfo" "Technical Info/Bugs" @TOC "Main" @{U}PowerWindows patches the following System-Routines:@{UU} Intuition/OpenScreen Intuition/OpenScreenTagList Intuition/CloseScreen Intuition/OpenWorkbench Intuition/CloseWorkbench Intuition/OpenWindow (V 0.9) Intuition/OpenWindowTagList (V 0.9) Intuition/CloseWindow (V 0.9) Intuition/ActivateWindow (V 0.9) Intuition/ActivateGadget (V 0.9) Intuition/WindowToFront (V 0.9) Intuition/WindowToBack (V 0.9) Layers/UpFrontLayer Layers/CreateUpFrontLayer Layers/CreateUpFrontHookLayer Layers/MoveLayerInFrontOf (V 0.9) @{U}Known Bugs:@{UU} - Windows that are out of Screen can't be brought to Back with the Window's Depth-Gadget: This is because Intuition always thinks it has to bring it to front be- cause such a Window is never the frontmost Layer. (PowerWindows creates some hidden Layers which are always in front of all normal Window- Layers) - The marker can trash the Screen (but not foreign memory): This is because my Input-Handler does the LockLayers() Call before drawing the Marker and Intuition's Input-Handler being the same Task is allowed to brake it. - Deadlocks can occure when you try to drag a Window while there is a lot of "Activity". Anyway PowerWindows intercepts them and after a short delay (1 second or so) you should be able to continue. - It is possible to use the Gadgets/Menus while dragging a window if you use Intuition's Shortcuts (LAMIGA+LCOMMAND, RAMIGA+RCOMMAND). You should not do that as the Screen will/might be trashed. @{B}Note:@{UB} This has been fixed in V 0.9!!! - If Intuition tries to close the Workbench-Screen, PowerWindows un-patches the Screen and WILL NOT re-patch it if closing fails (because of not closed Windows or something similiar). This will be fixed soon! @{U}Hints:@{UU} - Don't use Patterns with @{FG SHINE}TASK@{FG TEXT} and @{FG SHINE}ICONIFYTASK@{FG TEXT} if you know the real Names of the Programs. Pattern-Matching needs a lot of Stack and nobody knows what happens, if the Task opening the Screen/Window is too low on Stack. @{B}Note:@{UB} As a program opening a Screen/Window has/might have to scan all the Names, all the Names you specify must not have any Pattern in order to avoid this! @ENDNODE @NODE "History" "History" @TOC "Main" @{B}V 0.8@{UB} @{FG SHINE}26.01.97@{FG TEXT}: - First public release - Still in development - There are still some bugs @{B}V 0.9@{UB} @{FG SHINE}01.02.97@{FG TEXT}: - Rewrote program in "C". First Version was in Pascal. - Fixed Bug that caused trashing Screens' Depth-Gadget. These gadgets are RELRIGHT by default and therefore will not be correct while PowerWindows moves a window. (PowerWindows changes the Screen's Width and Height while doing this as you should know if you have read the documentation!) - Breaking the Program had a serious Bug. The Routine that resets the Patches seems to have returned always success even if it didn't succeed. Further, if it found, that a function has been patched by another program, it re-patched this function to PowerWindows' Routine. - Windows can now be iconified. You get a nice Gadget for this, which either looks like the ones in MUI or has a new look designed by me. - Lots of Bug-Fixes that could cause the program to hang. - Now there should be very few Deadlocks (which anyway are intercepted by the Deadlock-Hunter) - Lots of new Configuration-Options - Deadlock-Hunting is now done in a Sub-Task. @{B}V 0.9.1@{UB} @{FG SHINE}31.03.97@{FG TEXT}: - Added my EMail Address to documentation! - HardDisk ceased to work on 20.03.97, the day I finally got access to Internet (Arrgh!). - Version 1.0 will be released a little later than ex- pected! (Need a new HardDisk!) @ENDNODE @NODE "Future" "Future" @TOC "Main" 1) Preferences Program 2) Turn it into a commodity 3) External Iconify-Gadget Render-Routines 4) External Icon-Render Routines 5) Bug Fixes 6) CREATE AN UNREGISTERD VERSION WITH SEVERAL RESTRICTIONS, IMPLEMENT A SELF-DESTRUCTION ROUTINE OR CREATE A VIRUS THAT KILLS EVERY POWER- WINDOWS-EXECUTABLE IT ENCOUNTERS, IF YOU GUYS DONT START PAYING THE SHAREWARE FEE! 7) Look for a new HardDisk @{B}Note:@{UB} 1) has the lowest Priority. 7) has the highest Priority!!! @ENDNODE @NODE "Author" "Author" @TOC "Main" @{U}PowerWindows was created by:@{UU} Georg Steger Hochlercher 30 I-39030 St. Johann @{B}SOUTH TYROL - ITALY@{UB} @{U}Send Bug-Reports, Comments to:@{UU} EMail: steger@pass.dnet.it @ENDNODE @NODE "OtherStuff" "Other Stuff made by Georg Steger" @TOC "Main" @{FG SHINE}@{B}PowerCrawler V1.10 (SHAREWARE):@{UB}@{FG TEXT} A Map-Editor with incredible features. Have a look at the Screen-Shots! @{U}Features:@{UU} o Blocksize from 1 x 1 to 255 x 255 o Mapsize from 2 x 2 to 32767 x 32767 o Upto 10 Layers (not parallax) with Mask-Support o Localized o Userdefined Screenmodes/Fonts for Editscreen o Userdefined Font for Main Window on Workbench o Fontsensitive GUI o Userdefined Screenmode for BlockScreen o External Loader/Saver-Support o Many Draw-Tools (Freehand, Line, Rectangle, filled Rectangle, Airbrush,Fill) some with variable modes (vertical/horizontal Filling, OnePointPerRow/Column-Line, ...) o MAP-EDITING WITH VARIABLE ZOOM (1% - 100%) o Zoom Pre-Calculation for faster Editing o Fliptable for controlled flipping o Savable MAP-PREVIEW (1% - 100%) o Brushes. You can give them names, sort them, save them! o Mask-Creation inside program. Invert Mask. Load Mask as IFF-File. o Up to 6 projects in memory which can all have different settings, pictures, ... o Project-Saving/Loading which will save/load Map-Data,Settings, FileNames,Fliptable,Brushes,Mask in/from one file! o Shortcuts for nearly everything. o Popup-Menus for Brushes and Zoom. o Undo/Redo o Datatypes-Support o Iff-Library-Support o HAM/EHB-Mode-Support o Color0-Remapping and DRIPENS for good looking GUI in all modes! o OS-conform (hopefully) o Thousands of TOOLTYPES to change GUI, Flags for AllocBitmap, internal routines, ... o Loading/Saving settings to a file o Online Help @{U}How to get the registerd Version of PowerCrawler:@{UU} Send US$ 25 (DM 35) (LIRE 30000) @{B}CASH ONLY@{UB} to the following address: Georg Steger Hochlercher 30 I-39030 St. Johann/Ahrntal @{B}ITALY@{UB} EMail: steger@pass.dnet.it @{B}YOU @{U}MUST@{UU} INCLUDE: ONE EMPTY DISK RETURN STAMPS@{UB} @{FG SHINE}@{B}PowerIcons (Giftware):@{UB}@{FG TEXT} This little commodity removes the border around the Icons when you drag them. It makes color 0 of the Icons transparent. This program is especially useful if you use NewIcons V3. NewIcons already removed the border around the Icons but not when you dragged them. @ENDNODE