18.01.2008, 20:40:52
On the callbacks, exactly.
On the rest, first off, every DLL will have its own ini.![Smile Smile](https://forums.renegadeprojects.com/images/smilies/001.gif)
That has been planned exactly like that. Your DLL's INI should just not include "events" it does not use, because that would add unnecessary breakpoints, and every breakpoint will result in a DLL call.
The "issue of multiple DLLs hooking up to the same address" is no problem at all, not even in the same INI.
I'm not using Windows' INI parsing, I wrote my own. The Debugger is made so it accepts multiple breakpoints on one instruction.
I really do believe I've thought of most possible cases, but that we'll only see in its application...
On the rest, first off, every DLL will have its own ini.
![Smile Smile](https://forums.renegadeprojects.com/images/smilies/001.gif)
That has been planned exactly like that. Your DLL's INI should just not include "events" it does not use, because that would add unnecessary breakpoints, and every breakpoint will result in a DLL call.
The "issue of multiple DLLs hooking up to the same address" is no problem at all, not even in the same INI.
I'm not using Windows' INI parsing, I wrote my own. The Debugger is made so it accepts multiple breakpoints on one instruction.
I really do believe I've thought of most possible cases, but that we'll only see in its application...
![Wink Wink](https://forums.renegadeprojects.com/images/smilies/002.gif)