question about using scrolling dialog class

[ollydbg]

What is the necessary steps to use wxScrollingDialog ?
I just update my local copy of trunk( I have already scrolldialog patch by jens applied in my local copy), and I find some code are not build seccesully, so, I need change a little to let the compiler happy.

I think there are several steps:

1, change all the include statement:

Code

//#include <wx/dialog.h>

to

Code

#include "scrollingdialog.h"

2, change all the word

Code

wxDialog

to

Code

wxScrollingDialog

3, add "scrollingdialog.h"  under "F:\cb_svn\src\include\"

"scrollingdialog.cpp" under "F:\cb_svn\src\sdk\"

Am I right?
It seems I can build successfully.
Thanks.

[MortenMacFly]

Why don't you just use / inspect the scintilla branch? It's all applied / working there...

[Jenna]

That should be enough to use it (in most cases).
There are also changes to xtra_res.* to have an xml-handler for wxScrollingdialog, so it can be used in xrc-files.
The xml-handler hast to be loaded before any xrc-is loaded (this is done in app.cpp).
And of course changes to wxSmith, so it "knows" wxScrollingDialog.
If you have a wxs- or xrc-file containing a scrollingdialog, you have to manually change the appropriate cbp-files, because wxSmith uses tem to determine the type of the main-widget.
If a dialog is loaded from xrc via LoadDialog, this has to be changed to LoadObject with classname wxScrollingDialog (you need the xrc-handler in this case).
I don't know the version I introduced all these changes in the debugger- and scintilla testbranch, but if you look for the version scrollingdialog.* appears the first time, you should have it.

[MortenMacFly]

This raises another question in my head: When shall we merge the scintilla branch? I believe it's ready. I am using it daily (even the debugger branch which is scintilla + wxpropgrid refactoring + new debugger...).

[ollydbg]

Why don't you just use / inspect the scintilla branch? It's all applied / working there...

Thanks for the hint.

My major interest till now was improving CC plugin. , In my computer I also have a debugger_branch working copy(I haven't updated for several days), a "clean trunk working copy"( for test only).

Maintaining several working copies are not convenient for me.

For debugger plugin, I'm not sure the current debugger_branch has the "breakpoint" and "watch" persistent functionality.

[MortenMacFly]

For debugger plugin, I'm not sure the current debugger_branch has the "breakpoint" and "watch" persistent functionality.

I does not on SVN, but in my local copy.

BTW: You can safely use the scintilla branch and skip trunk. It'll be merged sooner or later anyways, is stable and features a lot of enhancements.

Hence the CC plugin in that branch misses the last commit to trunk. But I'll do a merge once the scripting engine is working (which is as of today... right?!). ;-)

[oBFusCATed]

For debugger plugin, I'm not sure the current debugger_branch has the "breakpoint" and "watch" persistent functionality.

It doesn't because I don't like the current situation with many files in the project folder. Would propose an API somewhere in time.