Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

External use of cbEditor

<< < (2/6) > >>

mandrav:

--- Quote from: dje on December 06, 2006, 03:06:50 pm ---What about the constructor ??
In header, there is
Note: you should not create a cbEditor object directly. Instead use EditorManager's methods to do it...

For sure I won't use EditorManager for creation as I want to be independant from the wxFlatNotebook...
Anything particular to know about construction requirements ??

--- End quote ---

Maybe you misunderstood something. You will not be able to create a new cbEditor, as a matter of fact I moved the constructors/destructor to protected scope.
But I have added a static function cbEditor::ApplyStyles(cbStyledTextCtrl*). Just feed this function with your cbStyledTextCtrl* and it will set it up like internal editors are setup.

Note: I haven't yet committed the above, but I will do so once I verify everything works as expected.

dje:
Ok, my SVN code from yesterday shew me public.

That's OK for me.

I can help you to test it in my case...

Thanks again,

Dje

mandrav:
Just committed what I posted in my previous message. Feel free to test it.

killerbot:
very interested in that plug-in :-)

dmoore:
off topic a little, but...


--- Quote from: mandrav on December 06, 2006, 02:48:52 pm ---Not now that we 're heading into the API freeze.

--- End quote ---

Does this mean you won't be doing anything with the debugger plugin API until v1.x?
(Since I'm the only one who seems to need changes to this part of API and the apparently the only person that uses my python debugger plugin, I'm not all that concerned, but it will help my planning to know what's in store.)

It would be nice if you could post a message sometime soon about this feature freeze.

Navigation

[0] Message Index

[#] Next page

[*] Previous page