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

BETA - Image Editor plugin

<< < (16/20) > >>

seb_seb0:
Hello,

I have updated the SVN (revision 61)

Changes:

BUGS SOLVED:
    1 - DragImage solved, wxGTK + wxMSW (without #define conditionnal compilation)
    2 - Zoom > 200% + Selection overlaps on left edge: selection is only partially drawn.
    3 - Context menu: when a mouse click close the context menu, it should not send a mouse click event (because it clears the selection)
    4 - Resizing selection: resizing once will paste the selection
                            loss of quality when resizing to original solved. However, it comes at the price of loosing mask information

IMPROVEMENT:
    1 - replace m_Image pointer by a direct object instance (simplify the code in several place)


Now I have solved all the (known) bugs, and I have implemented everything I wanted. Therefore I move the status to BETA.

What remains to do:
   1 - some documentation
   2 - some speed improvement on wxGTK

Let me know what you think !

Sebastien

seb_seb0:
Hello,

I have updated the svn repository (revision 64).

IMPROVEMENT:
    1 - catch events when environment settings are updated (to update wxAUI colors)
    2 - added some tooltips and help text (only in code. Not displayed yet). Work is still in progress.
    3 - SVN repository cleanup (removed the compiled files XPMEditor.cbplugin, XPMEditor.dll, XMPEditor.zip, test.bmp)

QUESTION FOR THE CODE::BLOCKS TEAM:
I am using wxAUI in my plugin. Since there are some Code::Blocks settings for wxAUI (menu Settings / environment / Docking system), I think it is better if the plugin uses the same settings as the IDE.
There are, at my knowledge, no events indicating that settings have been updated.
The only way I have found to know when settings are updated is to use a hack. I am using this notification update in Codeblocks/src/main.cpp
      
--- Code: ---void MainFrame::OnSettingsEnvironment()
                {
                  ...
                  Manager::Get()->GetLogManager()->NotifyUpdate();
                }
       
--- End code ---

I have therefore created a fake logger: it derives from the class
--- Code: ---Logger
--- End code ---
, but if does not create a control. It implements the UpdateSettings virtual methods, but none others. The result is that it works as expected, and it does not add an additionnal Tab in the log window.
In short, it does what I want.

However, I keep thinking it is a hack. Is it possible to add a Code::Blocks event when some settings are updated ?

Sebastien

seb_seb0:
Hello,

I have updated the SVN (revision 65)

CHANGES:

1- corrected a bug in wxDragImageExt: the transparent (masked) pixels of the image were drawn
2 - added tooltips to all controls. Currently adding context help strings (strings added in code, display needs to be done).

I continue working on help text. Then I will write a few html pages for online help. And then I will try to improve performances on wxGTK.

Sebastien

MortenMacFly:

--- Quote from: seb_seb0 on October 25, 2010, 09:36:40 pm ---QUESTION FOR THE CODE::BLOCKS TEAM:
There are, at my knowledge, no events indicating that settings have been updated.

--- End quote ---
That is true. If this makes sense for plugin we can think of an event. Nevertheless, you can always query configmanager if this setting is persisted (which is normally in the case for settings). That might be another option.

Besides that if you come up with a patch that's surely worth a look into.

seb_seb0:

--- Quote from: MortenMacFly on October 26, 2010, 09:07:36 pm ---
--- Quote from: seb_seb0 on October 25, 2010, 09:36:40 pm ---QUESTION FOR THE CODE::BLOCKS TEAM:
There are, at my knowledge, no events indicating that settings have been updated.

--- End quote ---
That is true. If this makes sense for plugin we can think of an event. Nevertheless, you can always query configmanager if this setting is persisted (which is normally in the case for settings). That might be another option.

Besides that if you come up with a patch that's surely worth a look into.

--- End quote ---

OK, I will try to do a patch - I believe it is a good functionnality.
I could also follow your other suggestion and regularly check the configuration file. But it is a bit overkill for just setting wxAUI colour. Therefore I will go with the patch.

Sebastien

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version