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

External use of cbEditor

<< < (3/6) > >>

mandrav:

--- Quote from: dmoore on December 06, 2006, 05:03:08 pm ---
--- 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.)

--- End quote ---

I 'm talking about the SDK API (sdk/*.h). Any plugin's interface can change without causing any problems. But the main SDK interfaces won't change after that.


--- Quote from: dmoore on December 06, 2006, 05:03:08 pm ---It would be nice if you could post a message sometime soon about this feature freeze.

--- End quote ---

There will be a public announcement a few days before we enter the freeze.

dje:

--- Quote ---Just committed what I posted in my previous message. Feel free to test it.
--- End quote ---

Great !!!  :D
It works as expected !!

Thanks for the evolution.

A problem still remains; I'd like to handle margin click and added this code :

--- Code: ---index = m_pSearchPreview->GetId();
Connect(index, -1, wxEVT_SCI_MARGINCLICK,   (wxObjectEventFunction) (wxEventFunction) (wxScintillaEventFunction)   &cbEditor::OnMarginClick );
--- End code ---

but cbEditor::OnMarginClick is private.
Is it possible to make it public too ?

Dje

dmoore:

--- Quote from: mandrav on December 06, 2006, 05:41:55 pm ---I 'm talking about the SDK API (sdk/*.h). Any plugin's interface can change without causing any problems. But the main SDK interfaces won't change after that.

--- End quote ---

in our last exchange, you hinted at changing the way debuggers are handled:


--- Quote ---What I plan to add soon is a language enum so that each compiler/debugger can report the languages it supports. Consequently, the editor will send breakpoint events to the debugger that should handle them.

--- End quote ---

would this not affect the SDK?

mandrav:

--- Quote from: dmoore on December 06, 2006, 06:39:31 pm ---would this not affect the SDK?

--- End quote ---

Have we entered the freeze yet and I 'm not aware? ;)

dje:
Hi !!


--- Quote ---but cbEditor::OnMarginClick is private.
Is it possible to make it public too ?
--- End quote ---

Waiting for an answer, I adapted the cbEditor::OnMarginClick in my class to handle only folding events.

I would like to use the default contextual menu.
I don't understand why the follwing code doesn't work:

--- Code: ---// Panel constructor
id = m_pSearchPreview->GetId();
Connect(id, wxEVT_SCI_MARGINCLICK,
(wxObjectEventFunction) (wxEventFunction) (wxScintillaEventFunction)
&FindOccurrencesView::OnMarginClick); // OK

Connect(id, wxEVT_CONTEXT_MENU,
(wxObjectEventFunction) (wxEventFunction) (wxContextMenuEventFunction)
&FindOccurrencesView::OnContextMenu); // KO

Connect(id, wxEVT_RIGHT_UP,
(wxObjectEventFunction) (wxEventFunction) (wxMouseEventFunction)
&FindOccurrencesView::OnMouseRightUp); // KO
// End of panel constructor


// m_pSearchPreview is a cbStyledTextCtrl*
void FindOccurrencesView::OnContextMenu(wxContextMenuEvent& event)
{
m_pSearchPreview->ProcessEvent(event);
}


void FindOccurrencesView::OnMouseRightUp(wxMouseEvent& event)
{
m_pSearchPreview->ProcessEvent(event);
}

--- End code ---

Any idea ??

When I use the EVT_CONTEXT_MENU and EVT_RIGHT_UP macros, the right clicks on panel are correctly handled, but not on cbStyledTextCtrl (for sure, no id provided...).

Thanks for support,

Dje

Navigation

[0] Message Index

[#] Next page

[*] Previous page