@database "Super-Request_DOCS" @REMARK History at the end. @REMARK .-----------------------------------------------------------------. @REMARK | Super-Request, HyperText docs written by P0T-NOoDLE of ANTHROX. | @REMARK `-----------------------------------------------------------------' @REMARK You need Multiview, AmigaGuide, or some other .Guide viewer. @REMARK Don't be a fucking loser and read this with a standard ASCII viewer!! @REMARK I have not included a non-Guide doc file to make you go and get @REAMRK AmigaGuide, coz it IS such a cool program. @REMARK $VER: Guide for Super-Request v1.00 (20-Feb-95) @NODE MAIN "Super-Request: Contents." .---------------------------------. .----------' Super-Request v1.00 [RELEASE 1] `---------. | Written by P0T-NOoDLE of ANTHR0X, (C)1995 Gods'Gift. | `------------------------------------------------------' RELEASED ..::::::. `-. For AmigaDOS v2.0 and above. .-' .::::.:. Feb-95 :.:::::::. `------------------------------' .:::::::: 100% Assembler Code. @{" DONATE: Children of the Storm " LINK Charity} @{" Description " LINK Description} @{" Features " LINK Features} @{" Requirements " LINK Requirements} @{" Usage " LINK Usage} @{" Examples " LINK Example_Script} @{" History " LINK History} @{" To Do " LINK ToDo} @{" Known Bugs / Problems " LINK Bugs} + My PGP Public Key > @{" Contacting the Author " LINK Contact} @{" Greetings " LINK Greets} Guide Checked by CheckGuide 1.0 by Eddy Carroll. @ENDNODE @NODE Description "Super-Request: Description." Super-Request is yet-another-requester program... It's a program which will pop-up a requester with a given title, message, and gadget(s), and return some value to whatever called it about which gadget the user pressed. Probably only usefull in scrips. Why did I write it? There have been quite a few programs which pop up requestors, and perhaps there are some that are as good as this one - however, I haven't seen them. I wanted to add some requestors to some of my other programs, and having spent about half an hour working out how to get EasyRequestArgs() to work in Assembler, I decided to turn it into a util on its own. So there you go, I wrote this because I was testing out some new routines, but I would not have released this had I not though that it offered some cool @{" features " Link Features} which I hadn't seen before. I must send thanks to Stefano Reksten: Althought certainly not the first person to write a Request util, his Request v1.2 was the one that I had lying around. Probably by accident, he used the 68020+ only Mulu.l instruction in his program and this caused it to guru on my Amiga. However, he did include his source and it's very easy for me to change the ".l" to a ".w"... The thing is, I only actually looked at his source after I had half coded Super-Request. I wasn't sure if I was using some of the structures correctly and remembered that I had his source in an archive, so I loaded it up and checked it out... (This is when I realised why it didn't work on my Amiga!) Anyway, his source confirmed that I was doing things correctly, so that is the first reason I have to thank him. I stress that, while I did look at his code for confirmation, I did not rip out any of his code (indeed, if you look at my coding it is totally different). Also, the way my Super-Request handles return codes is a little different to his Request, and my Super-Request also has several features not found in Request, which were really easy for me to add because I'd already written the code for other programs... Anyway: I hope you like it! @ENDNODE @NODE Requirements "Super-Request: Requirements" Super-Request requires: AmigaDos v2.0 or above (dos.library v36+, intuition.library v36+) That's it! Should work on any CPU, chipset, etc... Note that this program uses the standard intuition.library EasyRequestArgs() call and DOES NOT REQUIRE reqtools.library. This means that ANYONE can use it, and those (like me) who want reqtools requesters can just use RTPatch. @ENDNODE @NODE Features "Super-Request: Features" The features: - Optionally sets return codes for the IF WARN,ERROR,FAIL command. - Optionally sets a LOCAL variable for the best way to handle lots of different gadgets in a script. - Optionally beeps/flashes (depending on prefs) the screen. - You can specify the requester Title, Body, and Gadgets. - Body can be multiple lines. - As many gadgets as you want (within system limitations). - The requesters should be font sensitive. The usual Gods'Gift features: - 100% Assembler code (fast, not that such a small util could be slow!). - Pure (can be made resident). - Tested with MemMung. - NOT tested with Enforcer because I don't have a MMU. - Requires AmigaDOS 2.0+ (1.3 lamers can't use it). - Only has AmigaGuide docs (lamers who don't have AmigaGuide can't use it) @ENDNODE @NODE Usage "Super-Request: Usage." Typing "Super-Request ?" will bring up the ReadArgs() command template: @{" Help " LINK Arg_Help} (Switch) @{" Title " LINK Arg_Title} (String) @{" Body " LINK Arg_Body} (String) @{" Gadgets " LINK Arg_Gadgets} (String) @{" NoReturn " LINK Arg_NoReturn} (Switch) @{" Beep " LINK Arg_Beep} (Switch) @{" SetVar " LINK Arg_SetVar} (String) @{" About Return Codes and Local Variables " LINK Arg_Returns_N_Vars} A switch-argument is activated if it is given on the command-line. For example: "Super-Request Help" Activates the @{" Help " LINK Arg_Help} switch. A string-argument expects a string of text. For example: "Super-Request Title Request" Tells the program that the @{" Title " LINK Arg_Title} is "Request" To include spaces in your string, "surround it with quotes". To include quotes in your string, use *" instead of " For example: "He said *"HELLO*"!" = He said "HELLO"! If you're still confused, see the @{" Examples " LINK Example_Script} section. @ENDNODE @NODE Arg_Help "Super-Request: Usage, The 'Help' Argument." HELP Will bring up the more detailed help text. If the help switch is given, the rest of the command-line is ignored and no requester is poped up. Example: Super-Request Help @ENDNODE @NODE Arg_Title "Super-Request: Usage, The 'Title' Argument." TITLE This expects a string which will be the title of your requester. (The title is the text that appears in the drag bar). If you do not specify a title, "Request" is used as the default. Example: Super-Request Title "Important Message" @ENDNODE @NODE Arg_Body "Super-Request: Usage, The 'Body' Argument." BODY This expects a string which will be the body text of your requester. (The body text is that which appears in the centre of the requester, usually the main message or question which you want to convey). You can separate lines in the body text with a "|" char. (Currently, there is no way to include an actual "|" char in the body text without the program interpreting it as a new-line...) If you do not specify a body text, "Are you sure?" is used as the default. Example: Super-Request Body "This line appears above|This line!" @ENDNODE @NODE Arg_Gadgets "Super-Request: Usage, The 'Gadgets' Argument." GADGETS This expects a string which contains the name(s) of the requester's gadget(s). (The gadgets are the things you click on to get rid of the requester). If you want more than one gadget, separate each with a "|". ( As far as I know, it is not possible to include an actual "|" character in a gadget built by EasyRequestArgs() ). By convention, positive responses should be to the left and negative responses to the right. If you do not specify any gadgets, "OK|Canel" is used as the default. Example: Super-Request Gadgets "Yes|Maybe|No" See also: @{" About Return Codes and Local Variables " LINK Arg_Returns_N_Vars} @ENDNODE @NODE Arg_NoReturn "Super-Request: Usage, The 'NoReturn' Argument." NORETURN If this switch is given on the command-line, the program will ignore which gadget was pressed and always send return code zero (0) back to the shell (this is the standard return code to say "everything went OK"). This switch DOES NOT AFFECT the LOCAL VARIABLES. Example: Super-Request NoReturn See also: @{" About Return Codes and Local Variables " LINK Arg_Returns_N_Vars} @ENDNODE @NODE Arg_Beep "Super-Request: Usage, The 'Beep' Argument." BEEP If this switch is given on the command-line, the program will beep and/or flash the screen before generating the requester. The exact behaviour of this option can be controlled by the "Sound" preferences program as the program just calls DisplayBeep(). (The sound preferences program is usually @{" SYS:Prefs/Sound " system "run >NIL: SYS:Prefs/Sound"}. Note that even if you have the prefs set up to only Beep, the screen will flash if all audio channels are currently allocated). Example: Super-Request Beep @ENDNODE @NODE Arg_SetVar "Super-Request: Usage, The 'SetVar' Argument." SETVAR This requires the name of the local variable to set. Local variables are like the global environment variables stored in ENV: and ENVARC:, but they are local to the shell running the program. This means that you can use the same name for your variable and run the same script in two shells at once without them clashing with each other. If you do not specify a name, no variable will be set. Example: Super-Request SetVar GadgetNumber See also: @{" About Return Codes and Local Variables " LINK Arg_Returns_N_Vars} @ENDNODE @NODE Arg_Returns_N_Vars "Super-Request: Usage, Abount Return Codes and Local Variables." A program like this would not be half as usefull without the ability to determine the user's response and perform actions based on it, and this is what the return codes and local variables let you do... The local variables are quite a lot more powerfull than the return codes, but it is up to you which you use. They are each covered in their own sections: @{" Return Codes " Link Arg_OnlyReturns} @{" Local Variables " Link Arg_OnlyVars} See also: @{" Gadgets " Link Arg_Gadgets} @{" NoReturn " Link Arg_NoReturn} @{" SetVar " Link Arg_SetVar} @ENDNODE @NODE Arg_OnlyReturns "Super-Request: Usage, About Return Codes." By default, when you select a gadget, Super-Request will set a return code which can be acted upon by the "IF" command in a script. You can disable return code setting with the @{" NoReturn " Link Arg_NoReturn} command (which you might as well do when there is only one gadget, because you always know which gadget the user pressed). AmigaDOS and the IF command use the following return codes to represent the following things: .--------------------------. | DOS Number | IF Argument | |------------|-------------| | 0 | OK | | 5 | WARN | | 10 | ERROR | | 20 | FAIL | `--------------------------' Thus, "IF WARN" will be true if return code 5 has been set. If we number the gadgets "1, 2, 3, ... n" from left-right, they will generate the following return codes: .--------------------------. | Gad number | Return Code | |------------|-------------| | 1 | OK (0) | | 2 | WARN (5) | | 3 | ERROR (10) | | 4 | FAIL (20) | | 5 | FAIL (20) | | ... | ... | | 98 | FAIL (20) | | 99 | FAIL (20) | | ... | ... | | n (LAST) | FAIL (20) | `--------------------------' * All gadgets after the 3rd get "FAIL" (20) Note that the LAST GADGET ALWAYS GETS "FAIL" (20), even if the last gadget ---- is number 1, 2, or 3. Unless you have turned off Return Codes, you should always have the command "FailAt 21" (or above) in your script before Super-Request. This is so that the script does not abort if they choose the far-right gadget. (Of course, if you want the script to do that, don't have the failat!) If you're still confused about that, see the @{" Example Table " Link Arg_Ret_N_Var_Table}. Now, I'm assuming that you know how to use the IF command in a script... ...but if you want to see some examples of how it works, have a look at the @{" Example Script " Link Example_Script} (which comes as a separate file in the archive for you to execute and try out!). @ENDNODE @NODE Arg_OnlyVars "Super-Request: Usage, About Local Variables." Like the Return Codes, the Local Variables are used to determine which gadget was pressed from a shell. However, the Local Variables are much better, because different numbers are given for more than 4 gadgets, and because the value contained in the variable is not destroyed as soon as the next command is run (the return code is always from the last run program). Quite simply, when you give the @{" SetVar " Link Arg_SetVar} argument a name, such as "Gadget_Num", the program will set the named local variable to the number of the pressed gadget (numbered from left-to-right, but the LAST GADGET IS ALWAYS NUMBER 0 (ZERO)!!). So, if they pressed the 2nd gadget (and 2nd gadget is not the last one), it would be like you ran the command "Set Gadget_Num 2". .-----------------------. | Gad number | Variable | |------------|----------| | 1 | 1 | | 2 | 2 | | 3 | 3 | | 4 | 4 | | 5 | 5 | | ... | ... | | 98 | 98 | | 99 | 99 | | ... | ... | | n (LAST) | 0 | `------------------------' The LAST gadget is ALWAYS ZERO, no matter what number it is. If you're still confused about that, see the @{" Example Table " Link Arg_Ret_N_Var_Table}. The SetVar command only supports upto 99 gadgets and will output an error message if any gadget after the 99th is SELECTED (no error will be reported just because you specify 100 or more gadgets because the number of gadgets is not even looked at until one has been selected). This limitation should not cause any problems: I can't see anyone either wanting more than 99 gadgets or having a screen wide enough to fit 100 gadgets on! (I have tested the program with about 150 gadgets, and intuition starts to draw them overlapping and appears to ignore all but the first few when clicked on). Note that you need not worry about two scripts using the same local variable names because LOCAL variables are not shared like the GLOBAL environment variables stored in ENV: and ENVARC:. You can access local variables with the GET shell-command, but the easiest way is to put a "$" before the name, eg: Set Gadget_Num 2 Get Gadget_Num >> 2 or Set GadgetNum 2 Echo $GadgetNum >> 2 (Note that the Echo command doesn't appear to recognise variables with "_" in their names! I don't know if this is just the echo command or what, the Get command certainly works, as shown above...) You can use the IF shell-command in a script to do things if the variable is a certain number... eg: Super-Request Gadgets="Yes|Maybe|No" SetVar="GNum" IF $GNum EQ 1 ECHO "Selected YES" ENDIF IF $GNum EQ 2 ECHO "Selected MAYBE" ENDIF IF $GNum EQ 0 ECHO "Selected NO" ENDIF Now, I'm assuming that you know how to use the IF command in a script... ...but if you want to see some examples of how it works, have a look at the @{" Example Script " Link Example_Script} (which comes as a separate file in the archive for you to execute and try out!). @ENDNODE @NODE Arg_Ret_N_Var_Table "Super-Request: Usage, Table of Return Codes & Variables." .---------------------------------------------------------------------. | Gadgets | Choice | Return Code | Local Variable | |=============================|========|=============|================| | OK | OK | FAIL (20) | 0 | |-----------------------------|--------|-------------|----------------| | OK, Cancel | OK | OK (0) | 1 | | | Cancel | FAIL (20) | 0 | |-----------------------------|--------|-------------|----------------| | OK, Maybe, No | OK | OK (0) | 1 | | | Maybe | WARN (5) | 2 | | | No | FAIL (20) | 0 | |-----------------------------|--------|-------------|----------------| | All, Most, Some, None | All | OK (0) | 1 | | | Most | WARN (5) | 2 | | | Some | ERROR (10) | 3 | | | None | FAIL (20) | 0 | |-----------------------------|--------|-------------|----------------| | All, Most, Some, None, Quit | All | OK (0) | 1 | | | Most | WARN (5) | 2 | | | Some | ERROR (10) | 3 | | | None | FAIL (20) | 4 | | | Quit | FAIL (20) | 0 | `---------------------------------------------------------------------' You can see that with the Return Codes, you cannot tell between the fourth and fifth gadgets, while with the Local Variables, you can. @ENDNODE @NODE Example_Script "Super-Request: Example Script." Failat 21 ; Unless you use the "NoReturn" option, you MUST set Failat 21 or above ; as the last gadget will always set return code 20. ; First a simple information requester that Beeps. Super-Request Title="Information" Body="This script will test out|Super-Request for you..." Gadgets="OK" NoReturn Beep ; Now an example of how to use the return codes... Super-Request Title="Choices" Body="Pick one!" Gadgets="This|That" IF NOT WARN Super-Request Title="Congratulations" Body="You chose *"This*"|and not *"That*"" Gadgets "So I did!" ELSE Super-Request Title="Congratulations" Body "You chose *"That*"|and not *"This*"" Gadgets "So I did!" ENDIF ; Now an example of how to use the more flexible Local Variables... Super-Request Title="Do you love me?" Body="Would you fuck me?" Gadgets="YES!|Maybe...|If you PAY me!|No way, you SMELL!" SetVar="SReqDemo" IF $SReqDemo EQ 1 Super-Request Title="YOU DO LOVE ME!" Body="Great, I'll see you in bed tonight!" Gadgets="OK" NoReturn Beep ENDIF IF $SReqDemo EQ 2 Super-Request Title="How can I convince you?" Body="Would it help if I told|you I have a HUGE PENIS?" Gadgets="Sure Would!" NoReturn Beep ENDIF IF $SReqDemo EQ 3 Super-Request Title="Prostitution?" Body="Sorry, I'm broke..." Gadgets="Too bad" NoReturn Beep ENDIF IF $SReqDemo EQ 0 Super-Request Title="S0B S0B..." Body="Ohh! You've really upset me now!" Gadgets="GOOD!" NoReturn Beep ENDIF ; That's it really! Enjoy!, and don't forget that you can make it resident ; for speeding up long scripts!! Super-Request Title "That's it!" Body "Hope you enjoyed that...|Load up this script to see|how it all works..." Gadgets OK NoReturn @ENDNODE @NODE Contact "Super-Request: Contacting Mr.Nudel!" For those who want to check the PGP signatures: @{" My PGP Key " Link PGP_Key} (Of course someone could fake the signatures and put in a bogus key, but hopefully you'll be sure that this is not a fake and can use this key in later releases (or maybe you already have my key from a previous release and can compare it with this key to be more sure that it isn't a fake one (unless the same person faked both archives! Shit big conspiracy against Mr.Nudel!!))) You can reach me on any of the following UK Boards: --------------------------------------------------------------------------- Bad Dreams, Beyond Reality, Burger Bar, Cement City. --------------------------------------------------------------------------- You can EMail me via: --------------------------------------------------------------------------- M.Davidson@isode.com --------------------------------------------------------------------------- ...but if you do, please write "C/O Leo Davidson" as it is NOT MY ACCOUNT. (I probably won't even know you've written to me for at least a week if you do EMail me - I'd rather your called one of the above boards). @ENDNODE @NODE PGP_Key "Super-Request: P0T-NOoDLE's PGP Public Key." -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6ui (Amiga) mQBNAi89RoQAAAECANqcKhCP7W7aaOUlVoSXoFAkIJGfm9yB1WJAozUiD7uXVR5P qgVtzMXXYFPs8G6mOjnn7Bv+eTeCKnLDCXCfqb0ABRG0LkxlbyBEYXZpZHNvbiAt IFAwVC1OT29ETEUgb2YgR09EUydHSUZUL0FOVEhST1iJAFUCBRAvQo85KnLDCXCf qb0BAb6IAf94U5fnKo2ItCGOGWfbTWr8FHJ8jiP1q6vMUTkgQ2aoC1yUZ+XGmInC zxbSNspaMzhGRiWiUTpfWB8MAIXfMmno =2yTj -----END PGP PUBLIC KEY BLOCK----- @ENDNODE @NODE Greets "Super-Request: Greets." :-(==8 The cocksucker. \@:-) The shithead. }*{ A butterfly. ()() The fartknocker () || Just a prick... ()() 2-Cool (where is Swift...?) Aquarius (Cool, beautiful, well designed, feature packed utils!) Big Boss Bluelight (Sand Sucks!!) Carcass (FUCK!FUCK!FUCK!FUCK!FUCK!FUCK!FUCK!FUCK!FUCK!FUCK!FUCK!) Ciars Cruise Dream Warrior DreamScape (HUUUURRRRRRGGGGHHHH!) Hawkeye Hydro (Mr. SuntanOZ ?) Ice D Kool Falco (If I could call you, I would!) MDR (I wish CemCity was local, dammit!) MetalbasheR! (Long time no speak) Nightflyer (Hi, lover.) P0T-NOoDLE (at least I'll get a greet in SOMETHING!) Patriot Picard Sigma Seven (AmiNet CD rules! - Almost as much as hot chocolate?) Sweet Thing! (So, how BIG is he?) Thrash Vital Statistix (I wanna 28.8!) ...and Doc "Freedom is a human right, Skin don't matter, black or white." @ENDNODE @NODE Charity "Super-Request: Children of the Storm!" OK, this text is a few months old, and some new things have happened since then, but that shouldn't really matter! Please consider donating, even if you don't use this program! I know that most you out there won't pay anything at all, but I am doing this in the hope that at least a few people donate even a small amount of money, because every little penny can be put to some good! Please, at least read about the charity, Children of the Storm. I not going to say that anyone who doesn't send off some money should feel really guilty, just that anyone who does send off some money should feel really great, knowing that they've helped someone out. Even if you don't want to send any money (for whatever reasons), you could always send a letter of support, or spread the word to other people. I have never asked for any money for all the work I put into these utils, and I do not gain anything from your donations except knowing that I have helped some people out. I know that my work is used by a lot of people and that because of that, I have helped them out in one way or another, so why not help someone else now! Scene members do have hearts, don't they? Make it worth my while typing all of this info! Who are the CHILDREN OF THE STORM? ---------------------------------- In Britain this year, over a hundred young children will be accepted into the country by the Home Office, seeking political asylum. They may be just eleven or twelve years old. Often they have travelled across continents alone. They may have just lost their parents, seen brothers and sisters brutally murdered, or suffered beatings or torture themselves. Whilst our Government offers them basic shelter and the long-term possibility of war-refugee status in the UK, they can live here for weeks and months under the threat of instand deportation, sometimes forced to live rough without provision for food, clothing and other simple necessities. Far from their home and their culture, hungry, fearful and insecure, these children attempt, often with an astounding dignity and human spirit, to survive and grow despite the weight of unbearable memories they carry deep within... Background ---------- Since 1989 several members of the staff at Hampstead School have been building up a support network for refugee children attending the school who have little or no family back-up, few resources, and are often in a critical emotional state. Achievements to date include: - providing food, shelter and income for regugee children, working with the Tavistock Clinic which is providing counselling services and advising teachers, - forging links with the local authority (London Borough of Camden) to put children and carers in touch with any relevant support agencies, - establishing a social club in which refugee children are offered additional tuition and emotional support by their fellow pupils at the school, - acting as the children's advocates in relation to housing, social services, social security etc. Status ------ Registered Charity number 1035774 Consultant: Sheila Kasabova, Refugee Co-ordinator, Camden Council Consultant Psychologist: Maureen Fox, Consultant Psychotherapist at the Tavistock Clinic Legal Consultants: Bindmans (services at no charge) Accountants: Alan Heywood, Chartered Accountants (services at no charge) Aims and Objectives ------------------- 1 To continue to build on the existing project achievements outlined, 2 To extend knowledge acquired by staff and pupils of the school to other schools and bodies dealing with refugee children through teacher-training programmes, conferences, booklets etc. Summary of Projects in Progress or Anticipated ---------------------------------------------- 1 Publishing a booklet: the Hampstead Story, by those involved in the project, outlining the problems Hampstead School itself has encountered with refugee children and strategies for dealing with them. To be delivered free of charge to every school in the country. Cost: £9,000. Project in progress. 2 Expanding the social club outlined above to include students from other local schools including primary schools. Cost: £50 per month. Project in progress. 3 Employing a full-time counsellor at Hampstead School to counsel children and train staff in counselling techniques. Cost: £38,000 pa. 4 Employing an administrative assistant to manage the charity. Cost: £20,000 pa. 5 Holding a national conference on problems faced by refugee children in Britain, and strategies for overcoming them, open to any persons or organisations working with regugee children (teachers, welfare and social servicesm volunteer groups etc.) 6 Employing a fundraiser. Cost: £15,000 pa. Conclusion ---------- The project originated at Hampstead School is the only one of its kind. Due largely to recent wide coverage and acclaim in local, national and international media, it is increasingly being recognised by local authorities as a role model for other schools. Central to the project's success is teacher Athy Demetriades, who has assisted on training days in schools around the country. Regular requests for her to speak now come from solicitors, educational psychologists, welfare services and radio programmes as well as schools. On average, she fulfils one such engagement per week. She is, in effect, becoming one of few experts on the all-round care of children suffering a unique combination of problems - the destruction of the childhood together with the loss of citizenship and any automatic recourse to law and welfare that citizenship entails. Sponsorship for Children of the Storm would ensure that the work originated at Hampstead School can continue. It would also lay the foundations for a training programme enabling teachers and carers right across the country to provide the basics of security and education to refugee children. Further Information =================== This is basically what you would find on the letter head: Children Of The Storm Hampstead School Westbere Road London NW2 3RT United Kingdom There is a telephone and fax number, but I feel that it would be unwise to include it here, as there are a few idiots out there who might abuse it. Charity registration number 1035774 Patrons: Dame Judi Dench, Lindsay Duncan, Geraldine James, Griff Rhys Jones, John Gordon Sinclair. Trustees: A. Demetriades, A. Berkeley, M. Janota Bzowski, S. Pickford, G. Walker, M. Johnson, F. Capone. Consultants: M. Fox THE TAVISTOCK CLINIC, M. Martin LEGAL ADVISER, A. Heywood A.C.A, S. Kasabova CAMDEN L.E.A. The address is up there, so go on, donate! If you think you can offer something other than money, write! I want to say a huge thanks to anyone who does donate some money. My one request is that anyone donating money writes in their letter that they found out about the charity from this util. If you wish, include your scene-handle and I will make a list of everyone who has donated. Thanks for at least reading this... and sorry for any mistakes in the above text - my typing can go a bit haywire sometimes!! @ENDNODE @NODE Bugs "Super-Request: Known Bugs / Limitations." - No checks are done on how wide you're asking the gadget to be. If you specify more gadgets than can fit on the screen, intuition will start overlapping them and may ignore some of them. If you specify too wide a body text it will go off the screen. If you specify too wide a title text it will be clipped to size. >None of this is too bad (I don't think it will cause any crashes, just ugly requesters!), and it's not really a bug in either my program or intuition, it's just the way things are... Just keep it in mind if you're using a virtual/overscan/mega-hires screen that some people have 640x200 screens out there! - The @{" SetVar " Link Arg_SetVar} command will generate an error message and abort the command if a gadget greater than number-99 is selected. This should not cause any problems as 100 gadgets won't even fit on a screen in the current OS! (see the note above), and I doubt anyone would even want 100 gadgets!! That's it really! This program features as much error checking code as all of my others, which is overkill really, for something so simple, but the code was already there and it would've been more difficult for me to code it WITHOUT the code than with it! @ENDNODE @NODE ToDo "Super-Request: To Do." These are ideas which don't really matter to me, but I may add in the future (I probably won't, but if you'd like them, lemmy know!)... To Do: - Make it possible to use the "|" char in the @{" body " Link Arg_Body} without it causing a new-line. (Pretty easy to code, but hardly worth it?) - It would be cool if you could specify which public screen the requester should open on. (Cool, but could be a pain to code because I have to give it a window structure, not a screen one, dammit!) - Perhaps add support for the automatic cancelling of requesters using IDCMP flags (eg Insert a disk to cancel the requestor)... Probably not of much use, however, in most script situations... - I'm sure I had another idea, but I've forgotten it!... To NOT Do: - It would be very easy to make @{" SetVar " Link Arg_SetVar} handle over 100 gadgets, but currently intuition won't usually fit that many on the screen, and I can see no reason for anyone to want more than 100 gadgets in this kind of requester! (It's not a button-runner for Christ's sake!) @ENDNODE @NODE History "Super-Request: History." .=[*][*][*][*][*][*][*][*][*][*][*][*][*][*][*][*][*][*][*][*][*][*][*][*]=. [*] Version v1.00 [====] Release #01 [====] Released late Februrary 1995 [*] `=[*][*][*][*][*][*][*][*][*][*][*][*][*][*][*][*][*][*][*][*][*][*][*][*]=' - First public release. - No future updates planned, unless you have some ideas! See @{" To Do " Link ToDo} @ENDNODE @REMARK Dates in history, Contents, Version string.