hi Miller,
would you consider providing a mechanism for boxless graphs?
I.e. the graphs with non-text widgetbehavior when in !x->gl_isgraph state. It is now important for me to know, whether something like that is planned for the future, or if this is just a wild silly idea.
The reason is mainly selfish: not having such mechanism hampers my efforts both to design a poly~-alike external, and to finish coding `vex_multi' thing -- a vector collection being part of vexing library (release postponed, sorry).
Btw. it is a bit confusing to have a [graph] box left after clearing show-on-parent property of a graph, like one with an array in it, or one created with `graph' message to canvas, etc., while there is no such thing -- one cannot type "graph" into a box to make a graph. I am not suggesting that graphs other than subcanvases should be boxless, but either clearing their graph-on-parent flag should be prohibited, or text shown in the box should reflect a valid message to objectmaker.
Krzysztof
I don't understand this, sorry..
Do you just mean graphs without the drawn rectangular border??? Or something deeper that I'm not understanding yet...?
cheers Miller
On Tue, Feb 19, 2002 at 05:44:17PM +0100, Krzysztof Czaja wrote:
hi Miller,
would you consider providing a mechanism for boxless graphs?
I.e. the graphs with non-text widgetbehavior when in !x->gl_isgraph state. It is now important for me to know, whether something like that is planned for the future, or if this is just a wild silly idea.
The reason is mainly selfish: not having such mechanism hampers my efforts both to design a poly~-alike external, and to finish coding `vex_multi' thing -- a vector collection being part of vexing library (release postponed, sorry).
Btw. it is a bit confusing to have a [graph] box left after clearing show-on-parent property of a graph, like one with an array in it, or one created with `graph' message to canvas, etc., while there is no such thing -- one cannot type "graph" into a box to make a graph. I am not suggesting that graphs other than subcanvases should be boxless, but either clearing their graph-on-parent flag should be prohibited, or text shown in the box should reflect a valid message to objectmaker.
Krzysztof
hi Miller,
nothing deeper really, maybe a little more general. I mean being able to write an external, which might create a graph (aka canvas), and show it in a window, but to use a specialized handling of the way it is displayed on parent -- both when child window is open, and when it is closed.
The standard handling is to either show a text object box (if on-parent flag is off), or a rectangular area. There are several reasons one may want to change that (and no, hiding of a border is not that important):
- In a poly~-alike external I first create a specified number of
graphs, each acting as a single voice. Then user may want to look into (and edit!) any of the voices, i.e. open any of the graphs in a window. But the voice-graph cannot be shown on parent, neither as a graph, nor as an object box -- what is shown on parent is an object box of an external holding all the graphs. In this case the preferred solution would be to inhibit on-parent flag setting, and replace text_widgetbehavior (hard coded in graph_vis() routine) with a `hidden_widgetbehavior'.
- Also in another external I create a specified number of graphs,
each holding one array, but this time their _parent_ canvas is to be opened by clicking on an object box of an external. Now this parent canvas is causing trouble -- it is itself a subgraph of a graph in which an external object lives. It has to be invisible if on-parent flag is off, or show all the arrays otherwise. (And no, my external cannot simply mutate itself into a canvas_class.) One example of something slightly similar to what I try to make as vex_multi, is class-array of OpenMusic.
Well, in any case an ideal solution would be to subclass a canvas_class -- just a dream...
Krzysztof
(And sorry, when I want to be concise, I speak like a robofreak -- this is because of a fear of generating too much noise and sending it to the list.)
Miller Puckette wrote: ...
Do you just mean graphs without the drawn rectangular border??? Or something deeper that I'm not understanding yet...?
-
Krzysztof Czaja -
Miller Puckette