[PD] GUI to control [gemwin]

[Hans-Christoph Steiner]

State is a tricky things.  Most Pd objects have their own internal  
state, so that's not too complicated.  But [gemwin] is different  
since there is only one actual window and set of parameters, yet it  
can be accessed by multiple [gemwin] objects.

CVS is back, check in the pT stuff so we can put out a test release!

.hc

On Apr 4, 2006, at 10:37 AM, B. Bogart wrote:

> Hi Hans,
>
> The more I teach PD the more confused students are about the internal
> state of objects. For example:
>
> Create the usual toggle/number/metro/bang structure with 200ms as the
> default interval. Then send a number like "500" in the number box.  
> Then
> change the creation argument to 20. Now we have what looks like a  
> metro
> that should be at 500, since that was the last message sent, but the
> reinstanciation (which the students see are just editing the argument,
> which in tern means editing the internal interval, not reinstanciating
> the metro object) resets the interval to the argument.
>
> I like the idea of a bunch of pt.windows that all are "linked" to know
> the state of the window, but the problem is really that the internal
> state of most PD objects is by setting a value, even some defaults  
> seem
> illogical, [metro] without an argument seems to be 0ms, which could  
> be a
> pretty descructive default on a slower machine, depending on what its
> connected to.
>
> I need to look more at the multi-window stuff when the next stable
> version of Gem comes out, since they would greatly effect pt.window. I
> guess to follow the pervious lines of thought the gemcontrol would  
> be a
> new pT object and pt.window would stay analagous to gemwin.
>
> Lets take colour for example in pT we have sliders to set the color (I
> could add a canvas that shows the colour of the gemwin also) so if we
> have two pt.window's open then moving the red slider on one, should  
> move
> the red slider on the other...
>
> In the current version of Gem I saw some odd things happending with  
> two
> gemwins in the same patch... As I recall related to the gemwin colour.
>
> Hans, should I send you my working copy of pT so we don't have to wait
> for the CVS? (which could be forever at this rate)
>
> Frank, I've been thinking about adding Cyrille's trick also. :) It  
> would
> be great to have pT keep growing, as it can only move so fast with  
> only
> me! ;)
>
> .b.
>
>
>
> Hans-Christoph Steiner wrote:
>>
>> On Apr 2, 2006, at 10:22 AM, B. Bogart wrote:
>>
>>> Hey Hans,
>>>
>>> Why not contribute your changes to the pixelTANGO gemwin GUI.   
>>> pt.window?
>>
>>
>> I will, once sf.net CVS is back, and I can run your updated  
>> version  of pT.
>>
>>> What kind of "status" are you talking about since, like most  
>>> things in
>>> pd, the only way to know the status is to set it.
>>
>>
>> Just the current value of the various settings (lighting, fullscreen,
>> frame, create/destroy, rendering, etc.).  Since multiple [gemwin]
>> objects can point to the same window, it makes sense to have a   
>> querying
>> interface so that a new patch can query the gemwin to get  its  
>> status.
>>
>>> The main improvement I wanted to make was to add a popup for the
>>> fullscreen functionality, since you now specify "fullscreen 0",
>>> "fullscreen 1" (first screen) and "fullscreen 2"  (second screen)
>>>
>>> Also I was going to add stuff for the "dimen" message and add more
>>> resolutions to the popup list.
>>>
>>> Things like fps and profiling just use up cycles, so I don't  
>>> think it
>>> makes sense to be a constant thing, maybe just a message that  
>>> outputs
>>> the current fps once.
>>
>>
>> Yeah, I am not thinking of profiling.  Really, it should be the exact
>> same info you get when you send [print( to [gemwin], but in Pd-space.
>>
>>> PS: is there a scanf type external that does the opposite of
>>> makefilename:
>>>
>>> [symbol 640x480<
>>>  |
>>> [makeatom %dx%d]
>>>
>>> gives:
>>>
>>> 640 480
>>>
>>> prints either a list of all the atoms, or all the atoms out seperate
>>> outlets?
>>
>>
>> That would be nice.  Carmen proposed a POSIX lib for Pd, that would
>> definitely be part of it.  There could also be a more "Pd-ish" scanf.
>>
>> .hc
>>
>>
>>>
>>>
>>> .b.
>>> Hans-Christoph Steiner wrote:
>>>
>>>>
>>>> I made a GUI object to control the [gemwin] object that also  
>>>> displays
>>>> its status.  When a new instance is created, it queries existing
>>>> instances to get the status.  That way all instances will show  the
>>>> same
>>>> status.  I am planning on using this in the intro to Gem
>>>> tutorial/workshop that I am currently working on.  So feedback
>>>> would  be
>>>> appreciated.
>>>>
>>>> Is there any way to query [gemwin] directly?
>>>>
>>>>
>>>> .hc
>>>>
>>>>
>>>> ___________________________________________________________________ 
>>>> __
>>>> ___
>>>> ____
>>>>
>>>> "Looking at things from a more basic level, you can come up with  a
>>>> more
>>>> direct solution... It may sound small in theory, but it in
>>>> practice, it
>>>> can change entire economies."
>>>>                                                     - Amy Smith
>>>>
>>>>
>>>> ------------------------------------------------------------------- 
>>>> --
>>>> ---
>>>>
>>>> _______________________________________________
>>>> PD-list at iem.at mailing list
>>>> UNSUBSCRIBE and account-management -> http://lists.puredata.info/
>>>> listinfo/pd-list
>>
>>
>>
>> _____________________________________________________________________ 
>> ___
>> ____
>>
>>  As we enjoy great advantages from inventions of others, we  
>> should  be
>> glad of an opportunity to serve others by any invention of ours;  and
>> this we should do freely and generously.
>>                                                   - Benjamin Franklin
>>
>>


________________________________________________________________________ 
____

            "The arc of history bends towards justice."
                                            - Dr. Martin Luther King,  
Jr.