Re: [PD-dev] Ignoring '5401': doesn't look like a Pd-file

2010-01-16 Thread IOhannes zmölnig
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] Ignoring '5401': doesn't look like a Pd-file

2010-01-16 Thread Hans-Christoph Steiner


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] Ignoring '5401': doesn't look like a Pd-file

2010-01-14 Thread Hans-Christoph Steiner


On Jan 14, 2010, at 3:51 AM, IOhannes m zmoelnig wrote:


Hans-Christoph Steiner wrote:

Hey,

Everytime I run pd 0.43 from the command line like ./pd, I get this:

Ignoring '5401': doesn't look like a Pd-file


yes, here too :-)
and i even know where it comes from...
when you call ./pd-gui.tcl somefile.pd, it will request  
somefile.pd

to be opened (by calling open_file{}
if you call ./pd-gui.tcl 5400 it will connect to a running Pd on  
port

5400, but it will _also_ think that 5400 is a file to open, and call
open_file 5400
then open_file{} will do a check whether and will only ask Pd-core  
to

open the file if it ends with .pd/.pat/.mxt.
since 5400 does not match this criterion it will be discarded.

this is how it has been before i modified the source.
nobody noticed, because open_file silently dropped the illegal file.

what i did is, that i added a warning, if open_file{} discards a file
(because it does not end with .pd/...)
i think this is good, because it tells us, that we are using a bad  
hack

here: we are mixing 2 concepts
- the check in open_file{} is there to prevent bad files to be  
opened.

- if we call ./pd-gui.tcl 5400 we don't want to specify a file, but
instead a port! we know that this is a port, because it is a number.  
we
should not call open_file{} with something which we already know is  
not

a file.
so the check has to be done way earlier in the process.

in the meantime i prefer to see the warning (a constant reminder of  
the

quirk) rather than drop it.

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:


http://pure-data.svn.sourceforge.net/viewvc/pure-data?view=revrevision=12996

.hc



Man has survived hitherto because he was too ignorant to know how to  
realize his wishes.  Now that he can realize them, he must either  
change them, or perish.-William Carlos Williams




___
Pd-dev mailing list
Pd-dev@iem.at
http://lists.puredata.info/listinfo/pd-dev