SetPosPixel ( aOKPnt ) + // OK-Button-Position (at the bottom and centered) + Size aOKSureSiz = maOKSureButton. MaBuildInfoEdit ( this, ResId ( RID_CUI_ABOUT_FTXT_BUILDDATA, *rId. MaVersionText ( this, ResId ( RID_CUI_ABOUT_FTXT_VERSION, *rId. MaReadmeButton ( this, ResId ( RID_CUI_ABOUT_BTN_README, *rId. + maOKSureButton ( this, ResId ( RID_CUI_ABOUT_BTN_OK, *rId. MaOKButton ( this, ResId ( RID_CUI_ABOUT_BTN_OK, *rId. cxx (working copy - 283, 6 + 283, 7 :: AboutDialog ( Window * pParent, const ResId & rId ) : cxx (revision 1583953 ) +++ b /openoffice /trunk /main /cui /source /dialogs /about. cxx - a /openoffice /trunk /main /cui /source /dialogs /about. cxx b /openoffice /trunk /main /cui /source /dialogs /about. cxx =ĭiff -git a /openoffice /trunk /main /cui /source /dialogs /about. So first we add in the declaration in the header file: And requires modifying only two of the files. Cool! Let's hack! :-)įirst poke around a little and see that it does a couple of things and has an OK button, so let's keep the hack simple - we'll just add in a second OK button to make ourselves happy :-) All it would involve is duplicating the existing OK button to add in our new button and move it so it's visible. The dialog's resources are typically in the src file and the corresponding declarations in the hrc file. There is a cxx file that handles the dialog itself, which would most typically involve the declarations being placed in a hxx file. The resource files now () are located in svx/source/intro/Īnyway, with accompanying about.rc this would be the typical layout in OOo for most dialogs. The files that we will be modifying for this tutorial are: SourceMain="/cygdrive/c/./aoo-trunk/main" If we set SourceMain in cygwin to point to the main folder of aoo-trunk, by replacing. So doing a quick 'find -name *about*' in cui returns a set of results which also includes just the files we're interested in as well: about.hxx and about.cxx.
#APACHE OPENOFFICE BASE TUTORIAL CODE#
Well, I seem to love the About Dialog so much, so let's go poke the holy dialog itself - so we already know that the dialog is common across all the applications, so it would not be in their top-level projects, so it's probably in one of the others.Īnd what do we search for ? The OOo code follows a pretty nice naming convention, so you can guess that the About Dialog might just be named 'about', which in fact it is.
0 kommentar(er)
