As I said in a reply to Shawn, I would really like to see enabling/disabling searches implemented. Many moons ago, I took what I thought might be the first step by allowing searches to be enabled/disabled from the help window.
The only problem is that these 'disabled' searches are still loaded. They have to be loaded, at least partially, to display information about themselves. But, loading 250+ searches is directly related to the problem with the disappearing icons, and it takes way too long for startup/logins to complete. The only advantage in the current way they are disabled is that it prevents collisions. I.e., if I'm searching google news for "ebay": "ebay /news" there's a collision -- the ebay search fires when I just wanted to search the latest news for information about ebay. The next step is to _really_ disable searches. This would require the following... - Another method added to DQSDTools.dll that lets us rename files from script. - Modifying the help window code to: a) actually read all search files (both enabled and disabled) when it is displayed, instead of using the existing cache of already-loaded searches. The entire search would not need to be parsed, just the name and description. b) actually rename search files (e.g., *.xml_disabled) as they are disabled by clicking the checkbox. Thoughts? I'd love to see this implement, but I'm just not sure I have the time. Glenn ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ DQSD-Devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dqsd-devel
