Re: [PD-dev] Ignoring '5401': doesn't look like a Pd-file
Hans-Christoph Steiner wrote:
one could use the new ::pdwindow::verbose{} rather than post{}.
but really the underlying problem should be fixed sooner than later.
Warnings that happen every time rapidly become meaningless, and
therefore a pointless annoyance. Much better is to fix the underlying
problem:
yes, this is what i was saying.
http://pure-data.svn.sourceforge.net/viewvc/pure-data?view=revrevision=12996
this is what should have been done to fix the problem, and which i
didn't find time to do.
so in the end, it worked out exactly as i imagined:
- i added a more verbose output
- the new output hinted at a problem in the arg parsing
- someone got annoyed by the output
- the underlying problem was fixed
so i'm not sure whether there is a problem with the way i did.
so the next meaningless, and therefore a pointless annoyance to fix is:
WARNING: Font family 'Courier' not found, using default (courier)
let's see who makes the race
mfgasdr
IOhannes
signature.asc
Description: OpenPGP digital signature
___
Pd-dev mailing list
Pd-dev@iem.at
http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] pdwindow as syslog
Hans-Christoph Steiner wrote:
Hey IOhannes,
I was just looking thru your pdwindow.tcl procs. It seems to me that
those procs should just go all the way and implement a syslog-style
system with the same levels. Then the Pd window could have a little
dropdown menu on the lower left to select which level to show.
the pdwindow::verbose{} functionality is modelled after pd's verbose()
functionality.
assuming that most Pd devs will have more experience with Pd's posting
mechanisms than with a platform depending syslog functionality, it made
way more sense to use verbose than syslog.
if the only reason to change the name to syslog is, that the mechanism
reminds you remotely on that used by syslog, i would kindly ask to
change it back.
Attached is my failed attempt at defining the functions. Also, about
the tags for colorizing things, I think your syslog level tags and the
alternating linecolor? tags should be applied to all lines, not
depending on which proc is used. Then different plugins or modes can
colorize the text. Otherwise, it'll be just a big mishmash of colors.
please bear in mind that english is not my mother tongue.
...oh, it seems like the linecolor? does not finish the sentence.
then, i don't see what you mean: the public functions are
::pdwindow::verbose{}, ::pdwindow::error{} ::pdwindow::post{} are the
public functions that all set the corresponding tags.
so my argueing is, that tags should be applied to all text (which they
currently are), depending on which category a text belongs to.
the category is given implicitly by the proc that is used to print the
message. thus the tags are depending on which proc is used.
what i did change was to only call the colorizing code for a tag once,
and not each time something was printed. (which is somewhat useless and
only adds additional ressources)
As for me, I think just a subtle alternating color per post, not
per-line. Then error posts would have a sublte red background.
sure
fgmasdr
IOhannes
signature.asc
Description: OpenPGP digital signature
___
Pd-dev mailing list
Pd-dev@iem.at
http://lists.puredata.info/listinfo/pd-dev
[PD-dev] [ pure-data-Bugs-2933376 ] [pd-gui-rewrite] [declare -stdpath] expands relative to patc
Bugs item #2933376, was opened at 2010-01-16 13:14 Message generated for change (Tracker Item Submitted) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=478070aid=2933376group_id=55736 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: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: [pd-gui-rewrite] [declare -stdpath] expands relative to patc Initial Comment: It seems, that a [declare -stdpath] of pd-gui-rewrite expands the search pathes relative to the patch's location instead of relative to pd's installation location. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=478070aid=2933376group_id=55736 ___ Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] Ignoring '5401': doesn't look like a Pd-file
On Jan 16, 2010, at 4:46 AM, IOhannes zmölnig wrote:
Hans-Christoph Steiner wrote:
one could use the new ::pdwindow::verbose{} rather than post{}.
but really the underlying problem should be fixed sooner than later.
Warnings that happen every time rapidly become meaningless, and
therefore a pointless annoyance. Much better is to fix the underlying
problem:
yes, this is what i was saying.
http://pure-data.svn.sourceforge.net/viewvc/pure-data?view=revrevision=12996
this is what should have been done to fix the problem, and which i
didn't find time to do.
so in the end, it worked out exactly as i imagined:
- i added a more verbose output
- the new output hinted at a problem in the arg parsing
- someone got annoyed by the output
- the underlying problem was fixed
so i'm not sure whether there is a problem with the way i did.
so the next meaningless, and therefore a pointless annoyance to
fix is:
WARNING: Font family 'Courier' not found, using default (courier)
let's see who makes the race
mfgasdr
IOhannes
Ah, ok, it wasn't clear to me that you had an intention of fixing it.
Agreed on the font warning. I'd like to keep it there for a while to
get some more info on how it affects people, but for the final
release, people shouldn't see it unless there is an actual problem.
.hc
kill your television
___
Pd-dev mailing list
Pd-dev@iem.at
http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] pdwindow as syslog
On Jan 16, 2010, at 5:13 AM, IOhannes zmölnig wrote:
Hans-Christoph Steiner wrote:
Hey IOhannes,
I was just looking thru your pdwindow.tcl procs. It seems to me that
those procs should just go all the way and implement a syslog-style
system with the same levels. Then the Pd window could have a little
dropdown menu on the lower left to select which level to show.
the pdwindow::verbose{} functionality is modelled after pd's verbose()
functionality.
assuming that most Pd devs will have more experience with Pd's posting
mechanisms than with a platform depending syslog functionality, it
made
way more sense to use verbose than syslog.
if the only reason to change the name to syslog is, that the
mechanism
reminds you remotely on that used by syslog, i would kindly ask to
change it back.
While there is a verbose() function defined in s_print.c, it is
literally never used in the pd source. That's why I changed the name,
I didn't realize verbose() existed. It is used lightly in some
externals. If you really want it to be called verbose(), go for it.
Attached is my failed attempt at defining the functions. Also, about
the tags for colorizing things, I think your syslog level tags and
the
alternating linecolor? tags should be applied to all lines, not
depending on which proc is used. Then different plugins or modes can
colorize the text. Otherwise, it'll be just a big mishmash of
colors.
please bear in mind that english is not my mother tongue.
...oh, it seems like the linecolor? does not finish the sentence.
linecolor? is the tag name, ie linecolor0, linecolor1. I think the
tag should be renamed alternatingpost0, alternatingpost1 and have it
based on post rather than line.
then, i don't see what you mean: the public functions are
::pdwindow::verbose{}, ::pdwindow::error{} ::pdwindow::post{} are
the
public functions that all set the corresponding tags.
so my argueing is, that tags should be applied to all text (which they
currently are), depending on which category a text belongs to.
the category is given implicitly by the proc that is used to print the
message. thus the tags are depending on which proc is used.
what i did change was to only call the colorizing code for a tag once,
and not each time something was printed. (which is somewhat useless
and
only adds additional ressources)
IIRC, one function was posting with the linecolor0/1 tags and the
other with the verbose/syslog style tags. I am saying all posts
should have both a linecolor/alternatingpost tag and a verbose/syslog
level tag.
.hc
As for me, I think just a subtle alternating color per post, not
per-line. Then error posts would have a sublte red background.
sure
fgmasdr
IOhannes
I have the audacity to believe that peoples everywhere can have three
meals a day for their bodies, education and culture for their minds,
and dignity, equality and freedom for their spirits. - Martin
Luther King, Jr.
___
Pd-dev mailing list
Pd-dev@iem.at
http://lists.puredata.info/listinfo/pd-dev
[PD-dev] [ pure-data-Bugs-2933376 ] [pd-gui-rewrite] [declare -stdpath] expands relative to patc
Bugs item #2933376, was opened at 2010-01-16 08:14 Message generated for change (Comment added) made by eighthave You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=478070aid=2933376group_id=55736 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: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: [pd-gui-rewrite] [declare -stdpath] expands relative to patc Initial Comment: It seems, that a [declare -stdpath] of pd-gui-rewrite expands the search pathes relative to the patch's location instead of relative to pd's installation location. -- Comment By: Hans-Christoph Steiner (eighthave) Date: 2010-01-16 20:52 Message: An example patch is always very helpful, especially if it triggers the problem every time that it is run. Ideally the example patch would have only enough objects to cause the problem, but nothing else. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=478070aid=2933376group_id=55736 ___ Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
[PD-dev] [ pure-data-Bugs-2924862 ] print help
Bugs item #2924862, was opened at 2010-01-02 10:51 Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=478070aid=2924862group_id=55736 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: pd-extended Group: None Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Hans-Christoph Steiner (eighthave) Summary: print help Initial Comment: print help crashes pd in vista -- Comment By: SourceForge Robot (sf-robot) Date: 2010-01-17 02:20 Message: This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). -- Comment By: Hans-Christoph Steiner (eighthave) Date: 2010-01-02 16:01 Message: Please provide as detailed information as possible including which operating system (OS), CPU type, specific hardware, and the exact distro and version of Pd itself, etc. For example: Pd version 0.41.4-extended Mac OS X 10.5.7/Intel built-in sound -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=478070aid=2924862group_id=55736 ___ Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
