DataSeeker (ex ACDataSeeker)

History: -------- 20140602 1.13 fixed - Up/Down Icons, sorry no clue why they got corrupted

History: -------- 20140531 1.12 added - some usefull accelerators, F2 to open command line, F4 to edit file, F3 or ENTER to start searching changed - command line setting can now handle parameters. f.i. 'p:\4os2\4os2.exe @p:\4os2\4os2.ini "p:\4os2\4start.cmd & mode 81,101"' starts p:\4os2\4os2.exe with the rest of the line passed as parameter in directory of selected find result fixed - trap with DEBUG build and no search result

History: -------- 20100601 1.01: added - Spanisch version - bldlevel string changed - memory allocation grow step size from 512kB to 1MB fixed - translation for some strings was missing

History: -------- 20091228 0.54b: sorry I discovered a stupid bug in 0.53 fixed - crash when drive is specified and only 1 file search criteria - no drives but backslash defined leads to wrong double \\

History: -------- 20090319 0.51b: added - check on start if window is in visible area and move if not (f.i. if in another xpager window) - Drive selection window which is be used when no drive specifier is entered in 'Files to search for' - fixed ticket #2 - search options (recursive, case...) did not work without close and reopen DataSeeker

History: -------- 2008xxxx 0.47b: changed - First build from me (Andreas Buchinger). Lot of changes were necessary to build the GUI with URE. At this times, I don't want to build an application without a useful GUI editor. On OS/2 I think URE is the only usable one. There were a lot of changes necessary to get that beast compiled cleanly with my build enviroment. So maybe I've some things broken. While rebuilding the GUI, I've made some changes to the menus. I think they were not consistent with usual OS/2 look and feel. So I've changed that. fixed - crash when no editor or cmd shell is found in ini file - crash when no editor or cmd shell is entered in settings dialog added - support for MED and VS (VisualSlickEdit) as editors (beside EPM) - select first found text entry to start editor with approbiate line when double clicking on the file name - when opening a cmd shell, switch to it (put focus on the cli window) - add '*' if files to search is directory (simple check only - end with \ or :) 0.46: last version from Alessandro Cantatore I'm aware of

What's new Version 0.44 * - opening files via a double click on the entry in the listbox did not work if the file name contained spaces. * - searching on files containing NULs (i.e. characters with an ASCII value of 0) stopped at the first NUL. Now, in the search buffer, all NULs are replaced with spaces and so the whole file is searched. * - the product information dialog has been added. * - most help menu items now work.