ARACHNE TODOLIST - PROPOSED SOFTWARE CHANGE DETAILS ----------------------------------------------------------------------------------------------------- Item numbers refer to the 2DoList table. ITEM_29 Single right click inconsistency On the hotkeys.htm page single right click is supposed to delete text field line the same as Control-Y. While it does in some areas it does not using v1.73 at: Search F7 Write file Ctl-W Read file Ctl-R Is this a bug? ITEM_30 CSS format rgb() not supported Problem in CSS at http://www.drdos.org/ The problem lies in how they are designating the colors..... color: rgb(255, 255, 255); ( rather than: color: #fff or color: #ffffff , with or without the # ) Look at http://www.w3schools.com/css/css_colors.asp -- it seems that rgb() is another valid variant. While we're at it we might as well also enable rgb(n%,n%,n%) ITEM_31 Non-English character sets (charset switch; unikode support) I think my suggestions are important for all not-englisch users of DOS internet. 1. Make possible choossing with hand the *.cp file to translate body of the page. Sometimes there are no ; & how to transliterate TXT file?? 2. Unikode support can be make with special bigger CP file, in wchich for ex. byte nr 1050 should be latin letter for corresponding cirillic. I need also support for: - entities like #xfff; or #1050 ITEM_32 Mail displays as "(no subject)" The subject line in an incoming mail message: -------------------------------------------------------------- Subject: =?ISO-8859-2?Q?Jsme_dost_multimedi=E1ln=ED??= -------------------------------------------------------------- displays as "(no subject)" It is ONLY when 8859-2?Q is in the subject line; 8859-1Q is no problem, nor is ? in any other place in subject line. Sometimes it doesn't even wipe out the *entire* subject line, just part of it. ITEM_33 Erroneous Display of .BMP Image Clicking on the confirm link from 0spam.com anti-spam service gave me the usual "human operator" verification thing requiring me to type the number in the image into the box. However Arachne could not resolve the image as any visible number. These are small .bmp files. The file left in cache displays OK in other apps. An example is linked to the 2DoList table. You should be able to read the digits 4810 ITEM_34 'arachne -s' user interface 'arachne -s' lets you choose XMS, EMS or Disk. Then you get similar screen letting you choose VGA, EGA or CGA. Now things get tricky -- on my system the graphic screen that follows shows 'VGA' ticked (as you'd expect given the choice made in the last text screen), but in the top right of the screen it says 'VESA detected', which would lead you to think that the 'VESA' box, *not* the 'VGA' box should be ticked by default. (Indeed, since Arachne can detect the card type, the previous text screen seems to be useless at best, misleading at worst). Now, given that Arachne has detected VESA, one naturally goes down to the VESA choices on the right of the screen and picks one -- but unless you've remembered to move the left hand tick from VGA to VESA, the result is an error and suggested reboot. Perhaps there should be no VESA tick box on the left but a message telling you to pick one of the *specific* VESA choices on the right -- that way there is never more than one box ticked at any one time which should be more idiot proof than the current setup where two boxes need to be ticked for any given VESA setup. So I get the above figured out, tick the VESA box, then tick one of the VESA specific choices. Only 640 X 480 works without trouble. With any other selection, I get an 'errorlevel 0' message at the top of the screen, then I press a key and get to a graphical error screen that suggests a reboot ... even though there is nothing wrong! ... I can hit the 'restart Arachne' button with no problems, or just ignore the message and continue using Arachne at any resolution I want. I have an error report where there is no error. This is the sort of thing that could put a potential new user of Arachne right off. Furthermore, when one is making a choice in the graphical setup screen, the white 'VESA compatible card or driver' tag on the left seems to suggest that only the white choices on the right are available, even though they all can be made to work (inspite of the non-error mentioned above). Below the 'white' choices on the right are grey choices in blue text and grey choices in red text -- what's this all about? Can anybody confirm my experience? ... perhaps it's just due to my particular card. (On my other machine the 8 MB PCI card is detected as 'trident', so I can't make a fair comparison). It seems to me that this part of setup could be better managed -- opinions? Confirmed. It happens to me as well, regularly, on at least two machines with different hardware. This must be a very old problem, I got already used to live with it ;-)