[PD] GOP Patching woes

[marius schebella]

Hi,

it depends how big your window of the GOP is, when you save it. the parent
patch tries to resize the GOP (and everything in it) to the the size of the
window in which it appears in the parent patch.

to deal with that you have many different ways to go:

1a) try to resize the GOP patch until it fits like you want,
1b) try to resize the graph, where it appears in the parent patch using the
properties menu.

2) do this more precisely with a text editor. The last line (x-coords...)
contains the size of the patch.

Still, there are problems when opening a patch, that the size changes (by
two pixels each time you open and save it - at least with the windows
tcl/tk). For me I started to have the graphics in a seperate patch and have
an abstraction within it, which contains the patcher. In that case I dont
have to edit the size-stuff every time i change something in the GOP
(patcher), which was really annoying...

Marius.


----- Original Message ----- 
From: <ben at ekran.org>
To: <pd-list at iem.at>
Sent: Friday, September 12, 2003 4:30 PM
Subject: [PD] GOP Patching woes


>
> Hello all,
>
> Could someone explain why I had to make my patch look like
> (GOP_Patch.gif) in order to make it look like (GOP.gif) in the parent
> patch? Obviously there is some strange scaling going on plus some
> shifting depending on the type of GUI object (sliders and radios need to
> move over more, toggles and bangs end up about where you put them).
>
> Is anyone making GOPs that get compressed in the parent patch? Would it
> be reasonable to make GOPs work so that the upper left corner of the
> patch is repoduced (without scaling) in the parent up to the size
> imposed by the graph bounds. So that the GOP patches actually resemble
> the patches...
>
> Note I'm still using 0.36
>
> Or I could just be using GOP improperly...
>
> Thanks
> Ben
>
>
>