Aha... what this tells me is that the "savefn" and "propertiesfn" really shouldn't have been in the widgetbehavior structure (shared by all text objects) but in the "class" structure, with exported functions declared in m_pd.h. I'll try out a version of that for the next "test" release.
In general, at least one and possibly several major upheavals will still be needed in g_canvas.h in the future... I hope someday to be able to export a stable API for writing GUI objects but there's much work to do first.
The first big revision is to make it possible to delay graphics updates so they interefere less (hopefully not at all) with real-time computation. A second, possibly even bigger one, is to modularize out the TK code so people can plug in other GUIs such as WXWorks.
cheers Miller
On Tue, Aug 05, 2003 at 01:03:59PM +0200, Thomas Grill wrote:
the point is that, if a text object, due to a specialized savefn or propertiesfn, has its wb cloned (by whatever means) or defined from scratch, it is being visible on-parent, while it should not be. In other words, it is treated as a graphical object, while we want it to be handled as a text object.
Oh, i see, thanks. But then there will have to be some changes made to pd that are independent of the way how the wb is defined.
T
PD-dev mailing list PD-dev@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-dev