Changeset 1493
- Timestamp:
- Dec 28, 2009, 3:25:08 AM (16 years ago)
- Location:
- trunk
- Files:
-
- 7 edited
-
README (modified) (4 diffs)
-
dll/ipf/Trouble.ipf (modified) (1 diff)
-
dll/ipf/command.ipf (modified) (1 diff)
-
dll/ipf/context.ipf (modified) (1 diff)
-
dll/ipf/fm3.ipf (modified) (3 diffs)
-
dll/ipf/notebook.ipf (modified) (1 diff)
-
dll/ipf/tutor.ipf (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
trunk/README
r1468 r1493 524 524 =============== 525 525 526 FM/2 seems much slower than previous versions.527 The Find Buffer in FM/2 has been reworked to make it user528 settable in more place and significantly enlarge it. This529 significantly increases the loading speed for large directories530 However, most users will need to reset the buffer by going531 to the settings notebook scanning page and setting FindBuf.532 The new default for clean installs is 10240. We recommend you533 change to this setting (or higher) unless you have very limited534 hardware (less than 32 meg of memory original Pentium or earlier).535 536 526 If FM/2 won't run, the probable culprit is CONFIG.SYS. Your 537 527 LIBPATH statement should contain a ".;" entry. If yours … … 551 541 upgrade, first check the integrity of the install using 552 542 using WarpIN. If it shows a problem rerun the install 553 package. If that fails try installing to a new directory554 or backup your existing directory so you can save any changes543 package. If that fails try uninstalling with WarpIN and reinstalling. 544 Backup your existing directory so you can save any changes 555 545 you made to the template files then uninstall and reinstall. 556 546 Once you have FM/2 working migrate the *.ini, *.dat, *.tls, … … 574 564 FM3 2>STDERR.LOG 575 565 576 This technique works for all theFM/2, FM/2 Lite and all the566 This technique works for FM/2, FM/2 Lite and all the 577 567 standalone applets. 578 568 … … 581 571 FM2.LOG may be helpful. 582 572 583 584 573 Known problems/shortcomings: 585 574 =========================== 586 575 587 - FM/2 does not properly report sizes of some files with 588 long name resident on Win95/NT drives. 589 590 - File List Container fails to fill after drive change 591 SYS0039 error. 592 593 - Tree switching on Focus/Directory Change appears to be 594 slower than expected. 595 596 - Access to LS120 and FAT32 drives may be slower than expected 597 598 - Icon display in Directory Container does not always match 599 WPS icons 600 601 - Spurious WPS Objects Handles may be created during some 602 operations 603 604 - Trying to run Global.exe from the command line in 4OS2 605 (perhaps other shells) results in the execution of 4OS2's "Global" 606 command. Global.exe can be run by placing it in quotes or 607 prefixing it with *. See 4OS2's documentation for more information. 608 609 - As with any OS/2 program significant changes (such as our 610 change to OpenWatcom) will result in the incompatibility of 611 older (VAC) exes with new dlls and vice versa. Attempting to run 612 OpenWatcom exes with a VAC dll loaded in memory or in your 613 libpath ahead of the new version will result in a SYS3175 in 614 popuplog.os2. The reverse gives a SYS2070. If you experience these 615 problems search your libpath for fm3dll.dll and remove or rename 616 it. Your libpath should have "." (without the quotes) as your 617 first entry to minimize the likelihood of this problem. FM/2's 618 installer does not add the FM/2 directory to the libpath. 576 - See the section of this name in the FM/2 help file (FM3.hlp). 577 It is installed to the same directory as FM/2. 619 578 620 579 - See http://svn.netlabs.org/fm2/report/1 for a complete list of 621 580 currently active bugs 622 623 624 581 625 582 About FM/2: -
trunk/dll/ipf/Trouble.ipf
r797 r1493 55 55 in a SYS3175. If this occurs try accessing the directory using "open" from the context (popup) 56 56 menu. Mounting it using netdrives' vfat plugin also solves the problem. 57 :p. &endash. Move to trashcan is only active for local hard drive (this is a design limitation 58 of the xworkplace trashcan). The result will be a permanent delete for all other 59 drive types. Also be aware that deleted files are still retained on the drive 60 they were deleted from. The result can be full drive type errors. If you are 61 deleting to free up drive space you must either empty the trashscan or use 62 :hp6.Permanent Delete:ehp6. which deletes the files directly bypassing the trashcan. -
trunk/dll/ipf/command.ipf
r1419 r1493 61 61 :i1 id=aboutReorderingCommands.Reordering Commands 62 62 This dialog, accessed from the Edit Commands dialog, allows you to 63 rearrange the order of Commands. You take selected items from the left64 listbox and Add them to the end of the right listbox with the 65 :hp1.Add>>:ehp1. button. When you've moved everything to the right 66 listbox, click &OkayButton.. Click &CancelButton. if you change 67 your mind.63 rearrange the order that the Commands will be listed in the "Commands" 64 submenu. You take selected items from the left listbox and Add them 65 to the end of the right listbox with the :hp1.Add>>:ehp1. button. 66 When you've moved everything to the right listbox, click &OkayButton.. 67 Click &CancelButton. if you change your mind. 68 68 :p. 69 69 In reality, you don't need to move everything to the right listbox. You -
trunk/dll/ipf/context.ipf
r1441 r1493 374 374 may be recoverable. You also have the option of having the files moved to the 375 375 Xworkplaces/Eworkplace trahshcan from which they may be restorable.:link reftype=hd 376 res=99950.Delete = move to trashcan:elink. 376 res=99950.Delete = move to trashcan:elink.Move to trashcan is only active for local 377 hard drive (this is a design limitation of the xworkplace trashcan). The result 378 will be a permanent delete for all other drive types. Also be aware that deleted 379 files are still retained on the drive they were deleted from. 380 The result can be full drive type errors. If you are deleting to free up drive space 381 you must either empty the trashscan or use :hp6.Permanent Delete:ehp6. which deletes the 382 files directly bypassing the trashcan. 377 383 :artwork runin name='bitmaps\file.bmp'. :artwork runin name='bitmaps\fldr.bmp'. 378 384 :p. -
trunk/dll/ipf/fm3.ipf
r1486 r1493 714 714 10031 Deselect Mask N 715 715 &period... 716 4001 First Command Y 717 4002 Second Command Y 716 4001 - 4299 User Commands User settable 718 717 &period... 719 718 4900 First Toolbar N … … 721 720 &period... 722 721 :exmp. 723 Note&colon. Other Commands can also be used; just add to 4000 as required 724 to get the number of the command. For instance, Command 4 would be ID 725 4004. Command buttons use the text field; others shown have bitmaps 726 associated with them in FM/2's resources. Remember that if you change 727 your Commands around, you need to resync the tools to the Commands... 722 Note&colon. User commands can be used by entering the command's ID in the ID 723 text box; The command's ID is listed in braces following the command's title 724 on the "Commands" submenu (It is on the "Files" menu); Command buttons use 725 the text field; others shown have bitmaps associated with them in FM/2's resources. 726 If you wish to associate a bitmap with a command button name the bitmap using either 727 the command's ID (ie 4001.bmp) or the command's title (what ever you entered in the 728 "text" text box). The name isn't case sensitive (ie my command.bmp or My Command.bmp 729 would both work). Note: Reordering the commands no longer effects the commands ID 728 730 :p. 729 731 Note&colon. Toolbar buttons on a toolbar cause the appropriate toolbar … … 843 845 :li.32 means there is a user-defined bitmap for the button. 844 846 :ul compact. 845 :li.The bitmap must be in a file named <id-number>.bmp where <id-number> is the id number specified by the fourth line of the button definition.847 :li.The bitmap must be in a file named <id-number>.bmp or <text>.bmp where <id-number> is the id number specified by the fourth line of the button definition or the text is the text specified in the second line. 846 848 :li.The bitmap file must be in the FM/2 directory 847 :li.The bitmap must be 32x32 in size.849 :li.The bitmap should be 32x32 in size. Occasionally, this will seem to large if so try the bitmap resized to 28x28. 848 850 :eul. 849 :li.Add the senumbers together to combine the attributes. For example 9 (i.e. 8 + 1) means droppable with a spacer following.851 :li.Add the flag numbers together to combine the attributes. For example 9 (i.e. 8 + 1) means droppable with a spacer following. 850 852 :esl. 851 853 :li.The fourth line is the ID number of the button. See 852 :link reftype=hd res=96401. 853 Tool ID's 854 :elink. for more information. 854 :link reftype=hd res=96401. Tool ID's :elink. for more information. 855 855 :eul. 856 856 -
trunk/dll/ipf/notebook.ipf
r1483 r1493 716 716 permanently. If this is selected and you have the trashcan from Xworkplace 717 717 or Eworkplace installed the files will be moved to the trashcan for possible 718 later restore. 718 later restore. Move to trashcan is only active for local hard drive (this is 719 a design limitation of the xworkplace trashcan). The result will be a permanent 720 delete for all other drive types. Also be aware that deleted files are still 721 retained on the drive they were deleted from. The result can be full drive type 722 errors. If you are deleting to free up drive space you must either empty the 723 trashscan or use :hp6.Permanent Delete:ehp6. which deletes the files directly 724 bypassing the trashcan. 719 725 :p. 720 726 If the :hp6.Confirm target:ehp6. checkbox is checked, as it is by -
trunk/dll/ipf/tutor.ipf
r1419 r1493 349 349 :p. 350 350 There are three styles of deleting under FM/2 -- a "regular" delete, that 351 leaves the objects capable of being undeleted using OS/2's UNDELETE 351 leaves the objects capable of being undeleted using OS/2's UNDELETE (you must 352 have OS/2's del directories designated in config.sys -- this line is REMed 353 (not activated) when OS/2 or eComstation are installed) 352 354 command or FM/2's Undelete Utility, or uses the Xworkplace/Eworkplace 353 355 trashcan for file recovery, and a "permanent" delete that does
Note:
See TracChangeset
for help on using the changeset viewer.
