Hi Kai,
A few weeks ago, I've been working on the uicontrol implementation.
It's not completed yet, but I had to make some modifications to octave
code in order to support it in an efficient way. I also had (and still
have) to make some changes in the callback handling. One significant
change I made is to make use of the initialize/finalize/update methods
to control the graphic object creation/deletion, instead of doing all
the work in drawnow. I thought I'll let you know about it, in case you
had plan to work on this as well.
Just a remark about the implementation (if I understood it correctly):
isn't it overkill to recreate the whole menubar everytime something
changes?
Michael.
On Fri, Sep 24, 2010 at 11:33 AM, Kai Habel<address@hidden> wrote:
Hello all,
I have been working on the uimenu functionality lately. It allows the user
to create custom menus when using the fltk backend. I have attached two
changeset which implement the uimenu function:
Changeset.uimenu.go: Implements the uimenu graphic object and the respective
m-file. This changeset should be complete including Changelog, NEWS entry,
etc.
Changeset.uimenu.fltk: Implements the uimenu function using the fltk
backend. This changeset is for review so far. Since I expect some comments
and changes afterwards, I have not included the Changelog, etc.
I have tested it a lot on linux (32bit intel /intel graphic and 64bit
amd/nvidia graphic), but I may have missed some issues. Please give it a try
and report back problems you encounter. I am also interested in feedback
from Mac and Windows users. I hope Shai is back soon, so that he can have a
closer look ;-) I have attached a menu_test.m file for a quick test.
Q: How can I use "graphics.cc: xget_ancestor (const graphics_object&, const
std::string& )" in fltk_backend.cc? So far I have just copied the function.
I have noticed some problems with callbacks, I will report them to the bug
tracker later.
Kai