From: Hiroo H. <hir...@co...> - 2005-02-27 05:19:36
|
Jeff> I think I've written enough drivers/editors now to Jeff> have a fair basic understaning of how they work but I Jeff> don't fully understand why they were designed to work Jeff> the way they do. Jeff> Jeff> For instance here's one thing that I have never Jeff> understood. When you pull up the Get Patch dialog and Jeff> make your selections you're telling JSL which driver Jeff> and patch you want to request. When you hit the get Jeff> button, the selected driver sends the request to the Jeff> device and the device sends back the requested patch. Jeff> Then JSL searches through all the currently configured Jeff> drivers to try to figure out which driver the patch Jeff> belongs to. Why is this necessary when I just told it Jeff> what driver the patch belongs to? Good point. This is one of many reasons we made IPatch* interfaces. If your driver implements IPatchDriver interface directly instead of extending Driver class, it can bypass the unnecessary driver search. -- Hiroo Hayashi |