Patches item #3587404, was opened at 2012-11-14 22:29
Message generated for change (Comment added) made by millerpuckette
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3587404&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: puredata
Group: None
>Status: Pending
>Resolution: Accepted
Priority: 5
Private: No
Submitted By: IOhannes m zmölnig (zmoelnig)
Assigned to: Nobody/Anonymous (nobody)
Summary: ability to start multiple pd-guis
Initial Comment:
starting with Pd-0.43, pd-gui checks whether it is already running and tries to reconnect to the existing one.
while this is ok in some situations, it is an issue in other situations:
- when starting multiple instances of Pd on different desktops (i'm using the xfce window manager), the new instance will automatically focus the desktop of the already-running instance, which makes it difficult to separate those instances again (assuming that each instance has a number of windows open on startup)
- when using pd-gui to connect to a remote pd-core (while another instance of Pd is running on the same machines) is practically prohibited by this behaviour
it would be great if one could turn of this feature (at least when starting from the cmdline; and esp. when a <remotehost>:<remotport> is given...currently there is onl a check for remotport>5400 (when starting without <remotehost>)
----------------------------------------------------------------------
>Comment By: Miller Puckette (millerpuckette)
Date: 2013-01-03 14:26
Message:
This seems to work for me... I wish it were a bit less complex but I don't
see how to simplify it :)
----------------------------------------------------------------------
Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2012-12-18 11:40
Message:
updated the patch.
these are the tests i performed to check for compliance and bugfixes in
relation to the old implementation (as found in current git/master):
+ start "pd"
-> pd+gui starts up
+ start "pd abs1.pd"
-> pd+gui starts up with abs1 loaded
+ start "pd-gui"
-> pd+gui starts up
+ start "pd-gui abs1.pd"
-> pd+gui starts up with abs1 loaded
+ start 2 instances of "pd"
-> 2 guis pop-up (thus: 2* pd+gui)
-> when starting on separate desktops, each pd will stay on the desktop it
was started at (BUGFIX)
+ start 2 instances of "pd-gui"
-> the 2nd pd-gui exits after 3 seconds
+ start "pd", then "pd-gui"
-> the pd-gui exits after 3 seconds
+ start "pd", then "pd-gui", then "pd-gui"
-> both pd-gui's exit after 3 seconds
+ start "pd-gui", then "pd"
-> 2 instances of pd+gui start up
+ start "pd abs1.pd" and then "pd abs2.pd"
-> 2 guis pop-up (2* pd+gui), one with abs1.pd, the other with "abs2.pd"
-> when starting on separate desktops, each pd will stay on the desktop it
was started at (BUGFIX)
+ start "pd-gui abs1.pd" and then "pd-gui abs2.pd"
-> the 2nd pd-gui quits after 3 seconds, but abs2 gets loaded into the 1st
instance
-> focus is moved to the desktop of the 1st pd-gui
+ start "pd abs1.pd" and then "pd-gui abs2.pd"
-> the 2nd pd-gui quits after 3 seconds, but abs2 gets loaded into the 1st
instance
-> focus is moved to the desktop of the 1st pd-gui
+ start "pd-gui abs1.pd" and then "pd abs2.pd", and then "pd-gui abs3.pd"
-> 2 guis pop-up (2* pd+gui), one with "abs1.pd"+"abs3.pd", the other with
"abs2.pd"
-> when starting on separate desktops, the 1st 2 Pds will stay on separate
desktops, when starting the last pd-gui, it will switch to desktop#1 to
display abs3.pd (BUGFIX)
+ start "pd abs1.pd" and then "pd-gui abs2.pd" and then "pd-gui abs3.pd"
-> only one instance of Pd gets loaded, ending up with all 3 abs
-> when starting on separate desktops, all 3 abstractions will end up on
desktop#1
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2012-12-17 09:37
Message:
I don't think that's a good enough test. The one you removed is much
stricter: $argc == 1 When pd starts pd-gui, it only sends one arg: the
port number. If you want this to affect only remote connections, shouldn't
you make the test based on ::host?
----------------------------------------------------------------------
Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2012-12-17 08:37
Message:
attached is a patch (against todays git/master) that doesn't try to connect
to a running instance if the user provided a remoteport to connect to.
it re-uses the logic already implemented in parse_args().
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2012-12-14 20:25
Message:
Since you are the master of remote pd-guis, IOhannes, I'm assigning this to
you. It makes sense to me to base it on the host:port arg.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3587404&group_…
Patches item #3599169, was opened at 2013-01-01 19:10
Message generated for change (Comment added) made by millerpuckette
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3599169&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: puredata
Group: bugfix
>Status: Pending
>Resolution: Accepted
Priority: 5
Private: No
Submitted By: Hans-Christoph Steiner (eighthave)
Assigned to: Miller Puckette (millerpuckette)
Summary: make garray_getfloatarray 64-bit warning-stronger and better
Initial Comment:
This gets rid of the logic that only lets this message get printed once per Pd session. It also prints the array and patch name in question so people can hope to find the affected object. Since this problem means non-working objects, I think this warning should be loud and provide detailed info so that people know the cause and then go fix it :)
----------------------------------------------------------------------
>Comment By: Miller Puckette (millerpuckette)
Date: 2013-01-03 13:37
Message:
applied for 0.44
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3599169&group_…
hi,
I would like to try to maintain pix_opencv on several platform as far
as it's possible for me
so I would like to have SSH access to the compile farm
my ssh public key is attached
any objection ?
cheers
antoine
--
do it yourself
http://antoine.villeret.free.fr
Patches item #3589133, was opened at 2012-11-22 04:18
Message generated for change (Settings changed) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3589133&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: puredata
Group: None
>Status: Closed
>Resolution: Accepted
Priority: 5
Private: No
Submitted By: Jamie Bullock (postlude)
Assigned to: Miller Puckette (millerpuckette)
Summary: Patcher windows always open on "primary" monitor
Initial Comment:
Pd version tested with: 0.43.3 Vanilla
Steps to reproduce:
- connect a second monitor
- open Pd
- create a new patch and move it to the second monitor
- create a subpatch
Expected behaviour:
- the subpatch window opens on the same monitor as the parent patch
Actual behaviour:
- the subpatch window opens on the primary monitor
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2012-12-31 16:25
Message:
301 Moved Permanently I was suggested this website by my cousin. I am not
sure whether this post is written by him as no one else know such detailed
about my problem. You are incredible! Thanks! your article about 301 Moved
Permanently Best Regards Rolf Veronica
[url=http://noimi.com/blogs/viewstory/83095]Bridal gown[/url]
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2012-12-30 08:01
Message:
I must say, as very much as I enjoyed reading what you had to say, I
couldnt help but lose interest after a while. Its as if you had a great
grasp on the subject matter, but you forgot to include your readers.
Perhaps you should think about this from additional than one angle. Or
maybe you shouldnt generalise so significantly. Its better if you think
about what others may have to say instead of just heading for a gut
reaction to the subject. Think about adjusting your own believed process
and giving others who may read this the benefit of the doubt.
<a href="http://fit2wed.org/activity/p/50224/" title="Selecting
Proper">Selecting Proper</a>
----------------------------------------------------------------------
Comment By: Miller Puckette (millerpuckette)
Date: 2012-12-15 15:04
Message:
I didn't see the need to place the wondw over the object (patch number 2)
but applied the
first one to vanilla. Will mark this 'pending' pending...
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2012-12-14 18:36
Message:
The code was just always placing the new subpatch windows in the top left
corner of the main screen. I did two things in Pd-extended:
1. made the window placement logic aware of the full desktop size, not just
the main screen
http://pure-data.git.sourceforge.net/git/gitweb.cgi?p=pure-data/pd-extended…
2. made the window of new subpatches open near where the object was
placed.
http://pure-data.git.sourceforge.net/git/gitweb.cgi?p=pure-data/pd-extended…
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3589133&group_…
Patches item #3599169, was opened at 2013-01-01 19:10
Message generated for change (Tracker Item Submitted) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3599169&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: puredata
Group: bugfix
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Hans-Christoph Steiner (eighthave)
Assigned to: Miller Puckette (millerpuckette)
Summary: make garray_getfloatarray 64-bit warning-stronger and better
Initial Comment:
This gets rid of the logic that only lets this message get printed once per Pd session. It also prints the array and patch name in question so people can hope to find the affected object. Since this problem means non-working objects, I think this warning should be loud and provide detailed info so that people know the cause and then go fix it :)
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3599169&group_…
Bugs item #3599058, was opened at 2012-12-31 16:43
Message generated for change (Tracker Item Submitted) made by po-b
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3599058&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: externals
Group: v0.43
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Pierre-Olivier Boulant (po-b)
Assigned to: Nobody/Anonymous (nobody)
Summary: unauthorized/grid bug when in a GOP of an abstraction
Initial Comment:
I have some abstractions which have an unauthorized/grid in a GOP. I change the colour at start up with a message triggered by [initbang]
If I create the abstraction in a new patch, it creates fine but the object is visible in the parent patch and will disappear after moving the abstraction in the parent patch.
But the parent patch will not load once the patch has been saved with such an abstraction.
console output for example patch1:
(Tcl) INVALID COMMAND NAME: invalid command name ".x675f00.c"
while executing
".x675f00.c delete 6990b8GRID"
("uplevel" body line 1)
invoked from within
"uplevel #0 $cmds_from_pd"
If I create a subpatch with no GOP (example 2) it loads with an other error message:
(Tcl) INVALID COMMAND NAME: invalid command name ".x699530.c"
while executing
".x699530.c delete 67b460GRID"
("uplevel" body line 7)
invoked from within
"uplevel #0 $cmds_from_pd"
The same patch but with a GOP starts fine (example 4) and a patch with no subpatch or abstraction works fine too.
Windows 7 (64bit), Pd extended final RC (2012 12 31) 32bit
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3599058&group_…
Patches item #3589133, was opened at 2012-11-22 04:18
Message generated for change (Comment added) made by nobody
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3589133&group_…
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: puredata
Group: None
Status: Pending
Resolution: Fixed
Priority: 5
Private: No
Submitted By: Jamie Bullock (postlude)
Assigned to: Miller Puckette (millerpuckette)
Summary: Patcher windows always open on "primary" monitor
Initial Comment:
Pd version tested with: 0.43.3 Vanilla
Steps to reproduce:
- connect a second monitor
- open Pd
- create a new patch and move it to the second monitor
- create a subpatch
Expected behaviour:
- the subpatch window opens on the same monitor as the parent patch
Actual behaviour:
- the subpatch window opens on the primary monitor
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2012-12-31 16:25
Message:
301 Moved Permanently I was suggested this website by my cousin. I am not
sure whether this post is written by him as no one else know such detailed
about my problem. You are incredible! Thanks! your article about 301 Moved
Permanently Best Regards Rolf Veronica
[url=http://noimi.com/blogs/viewstory/83095]Bridal gown[/url]
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2012-12-30 08:01
Message:
I must say, as very much as I enjoyed reading what you had to say, I
couldnt help but lose interest after a while. Its as if you had a great
grasp on the subject matter, but you forgot to include your readers.
Perhaps you should think about this from additional than one angle. Or
maybe you shouldnt generalise so significantly. Its better if you think
about what others may have to say instead of just heading for a gut
reaction to the subject. Think about adjusting your own believed process
and giving others who may read this the benefit of the doubt.
<a href="http://fit2wed.org/activity/p/50224/" title="Selecting
Proper">Selecting Proper</a>
----------------------------------------------------------------------
Comment By: Miller Puckette (millerpuckette)
Date: 2012-12-15 15:04
Message:
I didn't see the need to place the wondw over the object (patch number 2)
but applied the
first one to vanilla. Will mark this 'pending' pending...
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2012-12-14 18:36
Message:
The code was just always placing the new subpatch windows in the top left
corner of the main screen. I did two things in Pd-extended:
1. made the window placement logic aware of the full desktop size, not just
the main screen
http://pure-data.git.sourceforge.net/git/gitweb.cgi?p=pure-data/pd-extended…
2. made the window of new subpatches open near where the object was
placed.
http://pure-data.git.sourceforge.net/git/gitweb.cgi?p=pure-data/pd-extended…
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3589133&group_…