wxperl-users

Re: [wxperl-users] Doc/View Framework

[Mattia B. <mb...@ds...>]

> Hi Mattia,
> 
> I have most of this working now. I'd like to get the wxFileHistory class
> working and tidy up a bit before I send a patch in.
Great!

> In all likelyhood this probably won't impliment 100% of the framework
> because I'm somewhat an XS\C++ novice, although I hope to be as close as
> possible. There's already enough to write an enhanced windows notepad with
> MDI, which I'll include for the /samples folder.
If you can put a list of missing things somewhere, it will be implemented

> I should be ready to send patch for review towards the end of the week. How
> do you want that?
For the new files, you can use a .zip (or .tar.gz, or .tar.bz2) archive.
For the modified files I'd like a patch made with either
diff -r -u -2
cvs diff -u -2

Thanks!
Mattia

RE: [wxperl-users] Doc/View Framework

[Simon F. <sim...@bb...>]

Hi,

I'm having a problem with the wxDocMDIParentFrame class. I'd like to be able
to override wxMDIParentFrame::OnCreateClient. To do that, you need to use
the default constructor for wxMDIParentFrame and then call Create() with the
params.

The problem is that wxDocMDIParentFrame just uses the constructor with the
params. Is there a way to get bypass the wxDocMDIParentFrame constructor?

I've tried variations on the following:

    ...

   public:
       wxPlDocMDIParentFrame(const char* package, wxDocManager* manager,
         wxFrame *parent, wxWindowID id, const wxString& title,
         const wxPoint& pos = wxDefaultPosition,
         const wxSize& size = wxDefaultSize, long style =
wxDEFAULT_FRAME_STYLE,
         const wxString& name = "frame")
          : wxDocMDIParentFrame(manager, parent, id, title, pos, size,
style, name),
            m_callback( "Wx::DocMDIParentFrame" )
       {
          Create(parent, id, title, pos, size, style, name);
          m_docManager = manager;	
          m_callback.SetSelf( wxPli_make_object( this, package ), TRUE);
       }

   ...

If there isn't a way to do this, do you think I should suggest to the
wxwindows dev team that wxDocMDIParentFrame use the two stage constuctor by
default? 

Thanks

Simon


BBCi at http://www.bbc.co.uk/

This e-mail (and any attachments) is confidential and may contain 
personal views which are not the views of the BBC unless specifically 
stated.
If you have received it in error, please delete it from your system, do 
not use, copy or disclose the information in any way nor act in 
reliance on it and notify the sender immediately. Please note that the 
BBC monitors e-mails sent or received. Further communication will 
signify your consent to this.

RE: [wxperl-users] Doc/View Framework

[Mattia B. <mb...@ds...>]

> I'm having a problem with the wxDocMDIParentFrame class. I'd like to be able
> to override wxMDIParentFrame::OnCreateClient. To do that, you need to use
> the default constructor for wxMDIParentFrame and then call Create() with the
> params.
> 
> The problem is that wxDocMDIParentFrame just uses the constructor with the
> params. Is there a way to get bypass the wxDocMDIParentFrame constructor?

<snip>

> If there isn't a way to do this, do you think I should suggest to the
> wxwindows dev team that wxDocMDIParentFrame use the two stage constuctor by
> default? 
Well, if you nned it, yes; the question is: since no-one (in C++) ever needed
this in probably 8 years, why do you need it (apart from the fact that it can
be done in wxMDIParentFrame).

Of course if you need it, I can commit the change myself.

Regards
Mattia

RE: [wxperl-users] Doc/View Framework

[Simon F. <sim...@bb...>]

> For the new files, you can use a .zip (or .tar.gz, or 
> .tar.bz2) archive.
> For the modified files I'd like a patch made with either
> diff -r -u -2
> cvs diff -u -2

No problem

What is the difference between wxPl... and wxPli... classes? I've named the
docview classes wxPl... because it's easier to type! But if I've
misunderstood the naming convention, I'm happy to change them before I
submit the patch.

Thanks

Simon


BBCi at http://www.bbc.co.uk/

This e-mail (and any attachments) is confidential and may contain 
personal views which are not the views of the BBC unless specifically 
stated.
If you have received it in error, please delete it from your system, do 
not use, copy or disclose the information in any way nor act in 
reliance on it and notify the sender immediately. Please note that the 
BBC monitors e-mails sent or received. Further communication will 
signify your consent to this.