Patches item #3596154, was opened at 2012-12-14 17:27
Message generated for change (Comment added) made by millerpuckette
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3596154&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: feature
>Status: Pending
>Resolution: Accepted
Priority: 5
Private: No
Submitted By: Hans-Christoph Steiner (eighthave)
Assigned to: Miller Puckette (millerpuckette)
Summary: split out window placement into proc so plugins can override
Initial Comment:
the first patch splits out window placement into proc so plugins can easily override it. This makes it easy for people to customize these calculations based on
their Window Manager, desires, etc.
The second patch gets the size of the full desktop area rather than just the screen size. For setups with multiple screens, these will be different. The 'winfo screenwidth' will be the width of the main screen while 'wm maxsize' gives the maximum possible size of a window, which includes all screens.
----------------------------------------------------------------------
>Comment By: Miller Puckette (millerpuckette)
Date: 2012-12-17 11:15
Message:
applied for 0.44
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2012-12-14 18:39
Message:
This makes it easy for people to customize these calculations based on
their Window Manager, desires, etc. Unfortuantely, Tk/X11 makes it hard
because it doesn't give you the measurements of the window chrome, only the
window contents. more info here:
http://lists.puredata.info/pipermail/pd-list/2012-10/098138.html
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2012-12-14 18:31
Message:
I added a second patch which modifies this one that makes pdtk_canvas_new
use screen size of full desktop area, not only the main screen. The 'winfo
screenwidth' will be the width of the main screen while
'wm maxsize' gives the maximum possible size of a window, which includes
all screens whe there are more than one.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3596154&group_…
Patches item #3595365, was opened at 2012-12-12 14:32
Message generated for change (Comment added) made by millerpuckette
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3595365&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: feature
>Status: Pending
>Resolution: Accepted
Priority: 5
Private: No
Submitted By: Hans-Christoph Steiner (eighthave)
Assigned to: Miller Puckette (millerpuckette)
Summary: Win32: make double-clicking open in same instance
Initial Comment:
This patch implements check_for_running_instances with the 'dde' package to support double-clicked files opening in the running instance of Pd. This is the Windows version of the GNU/Linux logic and it works the same. If pd-gui is started first, then this logic is activated. To use this functionality, the file associations needs to be setup to associate double-clicked files with pd-gui rather than pd.exe. Also, the standard Tcl library 'dde' must be included with Pd.
----------------------------------------------------------------------
>Comment By: Miller Puckette (millerpuckette)
Date: 2012-12-17 11:08
Message:
applied for 0.44
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3595365&group_…
Patches item #3395438, was opened at 2011-08-20 11:16
Message generated for change (Comment added) made by millerpuckette
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3395438&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: Closed
Resolution: Fixed
Priority: 5
Private: No
Submitted By: IOhannes m zmölnig (zmoelnig)
Assigned to: Miller Puckette (millerpuckette)
Summary: minor compat fixes for new buildsystem
Initial Comment:
some problems have been reported [1], because the old configure based buildsystems in some rare cases conflicts with the new autotools based buildsystem.
the problem only appears on systems with case-insensitive filesystems (w32, osx), where the new buildsystem might be tricked into used src/makefile.in rather than src/Makefile.in
imo, the best solution would be to get rid of one of the build-systems entirely (which hopefully means to move to the shiny new one :-))
if this is not feasible for now, the attached patch proposes a workaround, by renaming the conflicting files in the new build system, so they won't clash on case-insensitive filesystems.
here's a longer explanation of the problem and its solution:
right now, there are 2 build-systems, based con autoconf:
- the olde one, living in ./src/, which uses ./src/makefile.in to generate
./src/makefile
- the new one livong in ./, which uses ./src/Makefile.am to generate
./src/Makefile.in to generate ./src/Makefile
the two buildsystems can co-exist happily, except if the host filesystem is
case-insensitive, in which case the "new" buildsystem might be tricked into
using (erroneously) ./src/makefile.in
this patch renames the src/Makefile* (for the new buildsystem) to
src/GNUmakefile*, so there is no name conflict on case-insensitive systems.
NOTE: GNU make will look for the makefiles GNUmakefile, makefile, and Makefile,
in that order. the "old" buildsystem is unaffected, as there will never be a
"GNUmakefile" (only "GNUmakefile.am" and eventually "GNUmakefile.in").
[1] https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3395280&group_…
----------------------------------------------------------------------
>Comment By: Miller Puckette (millerpuckette)
Date: 2012-12-17 10:32
Message:
yep :)
----------------------------------------------------------------------
Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2012-12-17 03:07
Message:
seems like the old buildsystems is gone for good.
----------------------------------------------------------------------
Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2011-09-21 11:06
Message:
i totally agree with hans.
however, until the old system is ditched, i would still favour if these
workarounds could be added
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2011-09-21 10:59
Message:
I vote for ditching the old build system, I think its quite well tested
these days.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3395438&group_…
Patches item #3587404, was opened at 2012-11-14 22:29
Message generated for change (Comment added) made by eighthave
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: Open
Resolution: None
Priority: 5
Private: No
Submitted By: IOhannes m zmölnig (zmoelnig)
Assigned to: Miller Puckette (millerpuckette)
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: 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 #3587404, was opened at 2012-11-14 22:29
Message generated for change (Settings changed) made by zmoelnig
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: Open
Resolution: None
Priority: 5
Private: No
Submitted By: IOhannes m zmölnig (zmoelnig)
>Assigned to: Miller Puckette (millerpuckette)
>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: 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 #3596865, was opened at 2012-12-17 02:58
Message generated for change (Comment added) made by eighthave
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3596865&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-dev
Group: None
Status: Open
Resolution: None
Priority: 7
Private: No
Submitted By: IOhannes m zmölnig (zmoelnig)
Assigned to: Miller Puckette (millerpuckette)
Summary: re-adding sys_close() for ABI compatibility
Initial Comment:
in a recent patch to Pd-0.44, the sys_close() function was removed (and replaced by a macro to close()) on non-w32 platforms.
this breaks ABI-compatibility for externals that use sys_close() and have been compiled against Pd-0.43 (e.g. Gem, as currently packaged in Debian).
the attached patch re-introduces sys_close() and also provides implementations for sys_open(), sys_fopen() and sys_fclose() on non-w32 platforms.
the patch reduces the total number of ifdefs in the code :-)
----------------------------------------------------------------------
>Comment By: Hans-Christoph Steiner (eighthave)
Date: 2012-12-17 07:43
Message:
makes sense to me, I'm including it in Pd-extended
----------------------------------------------------------------------
Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2012-12-17 03:05
Message:
raising priority since it really prevents some externals from being loaded
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3596865&group_…
Patches item #3596868, was opened at 2012-12-17 03:11
Message generated for change (Tracker Item Submitted) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3596868&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-dev
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: IOhannes m zmölnig (zmoelnig)
Assigned to: Miller Puckette (millerpuckette)
Summary: use HAVE_STDINT_H for including stdint.h
Initial Comment:
this is a follow-up for commit:5459876b16 that includes stdint.h.
the patch uses HAVE_STDINT_H to include the header, and only uses hand-crafted types as fallbacks (i envision the time when MSCV will be C99 compatible!)
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3596868&group_…
Patches item #3395438, was opened at 2011-08-20 11:16
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3395438&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: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: IOhannes m zmölnig (zmoelnig)
Assigned to: Miller Puckette (millerpuckette)
Summary: minor compat fixes for new buildsystem
Initial Comment:
some problems have been reported [1], because the old configure based buildsystems in some rare cases conflicts with the new autotools based buildsystem.
the problem only appears on systems with case-insensitive filesystems (w32, osx), where the new buildsystem might be tricked into used src/makefile.in rather than src/Makefile.in
imo, the best solution would be to get rid of one of the build-systems entirely (which hopefully means to move to the shiny new one :-))
if this is not feasible for now, the attached patch proposes a workaround, by renaming the conflicting files in the new build system, so they won't clash on case-insensitive filesystems.
here's a longer explanation of the problem and its solution:
right now, there are 2 build-systems, based con autoconf:
- the olde one, living in ./src/, which uses ./src/makefile.in to generate
./src/makefile
- the new one livong in ./, which uses ./src/Makefile.am to generate
./src/Makefile.in to generate ./src/Makefile
the two buildsystems can co-exist happily, except if the host filesystem is
case-insensitive, in which case the "new" buildsystem might be tricked into
using (erroneously) ./src/makefile.in
this patch renames the src/Makefile* (for the new buildsystem) to
src/GNUmakefile*, so there is no name conflict on case-insensitive systems.
NOTE: GNU make will look for the makefiles GNUmakefile, makefile, and Makefile,
in that order. the "old" buildsystem is unaffected, as there will never be a
"GNUmakefile" (only "GNUmakefile.am" and eventually "GNUmakefile.in").
[1] https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3395280&group_…
----------------------------------------------------------------------
>Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2012-12-17 03:07
Message:
seems like the old buildsystems is gone for good.
----------------------------------------------------------------------
Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2011-09-21 11:06
Message:
i totally agree with hans.
however, until the old system is ditched, i would still favour if these
workarounds could be added
----------------------------------------------------------------------
Comment By: Hans-Christoph Steiner (eighthave)
Date: 2011-09-21 10:59
Message:
I vote for ditching the old build system, I think its quite well tested
these days.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3395438&group_…
Patches item #3596865, was opened at 2012-12-17 02:58
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3596865&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-dev
Group: None
Status: Open
Resolution: None
>Priority: 7
Private: No
Submitted By: IOhannes m zmölnig (zmoelnig)
Assigned to: Miller Puckette (millerpuckette)
Summary: re-adding sys_close() for ABI compatibility
Initial Comment:
in a recent patch to Pd-0.44, the sys_close() function was removed (and replaced by a macro to close()) on non-w32 platforms.
this breaks ABI-compatibility for externals that use sys_close() and have been compiled against Pd-0.43 (e.g. Gem, as currently packaged in Debian).
the attached patch re-introduces sys_close() and also provides implementations for sys_open(), sys_fopen() and sys_fclose() on non-w32 platforms.
the patch reduces the total number of ifdefs in the code :-)
----------------------------------------------------------------------
>Comment By: IOhannes m zmölnig (zmoelnig)
Date: 2012-12-17 03:05
Message:
raising priority since it really prevents some externals from being loaded
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3596865&group_…
Patches item #3596865, was opened at 2012-12-17 02:58
Message generated for change (Tracker Item Submitted) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3596865&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-dev
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: IOhannes m zmölnig (zmoelnig)
Assigned to: Miller Puckette (millerpuckette)
Summary: re-adding sys_close() for ABI compatibility
Initial Comment:
in a recent patch to Pd-0.44, the sys_close() function was removed (and replaced by a macro to close()) on non-w32 platforms.
this breaks ABI-compatibility for externals that use sys_close() and have been compiled against Pd-0.43 (e.g. Gem, as currently packaged in Debian).
the attached patch re-introduces sys_close() and also provides implementations for sys_open(), sys_fopen() and sys_fclose() on non-w32 platforms.
the patch reduces the total number of ifdefs in the code :-)
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=3596865&group_…