Greets,

i just downloaded the new version 1.09a and found the "plugin location" option does not work for me. I've been waiting for this feature some time.

I've specified an existing sub directory but ollydbg doesnt load any plugins.
("Plugin path" in ollydbg.ini contains the path)
If i copy the plugins into same directy ollydbg resides, the plugins are loaded.

Besides, the "udd location" option works. It loads and saves to specified directory.

Well .. one big user interface critique goes to configuration/options dialog.

The new options (tabbed property pages) are now accessed with one additional
button (in left bottom corner of debugging settings) - which violates windows user interface guidelines - it confuses the user.

Additionally the growing number of "configurable" items in ollydbg are accessed through an increasing number of tabbed property pages - which is user interface nighmare.

I suggest the use of a tree control to navigate option property pages for cleaner user interface.
A good example how this looks can be found here:

http://www.codeproject.com/property/TreePropSheet/WinXP.png

Much cleaner and easier to navigate (beside many commercial software uses this ui design to handle its sheer number of configuration options).

Anyway keep up the good work .. looks very promising ;-)

Regards,

A.Focht

Focht: do you mean 1.09b ?
* the plugins dir works for me, even for long dir name (with spaces too)
* "additional button" left button access the "Appeareance" dialog, which was present in old versions too. it's there for easy configuring all items. i agree with a tree based config option (i suggest it long time ago )

Hello,



of course not ;-)



Yesterday i found 1.09a the lastest (and tested it)... now 1.09b - a really fast fix ;-)
The plugin works now in 1.09b.

One possible problem:

I noticed some plugins have now problems with their persistent data (access to ini files ...).
I assume they use GetCurrentDirectory() which of course points to ollydbg base dir. To access the files in plugin dir:

- use the full module load path and strip the plugin name from it
- read the ollydbg plugin path from ollydbg.ini (not preferrable, ini options may change)

Regards,
A. Focht.