Nicola Pero wrote:
pedanticAn 'error', for the programmer using the base library, is when
the base library generates an exception. Anything else is not an error.
A nil return here indicates that the file doesn't exist, is not readable
or can't be read. This is considered a valid result,
Richard Frith-Macdonald wrote:
Nicola Pero wrote:
Ok - it looks silly to discuss too much about this anyway (with all the
pending stuff) but I can't avoid another one on this :-)
I don't understand why you are assuming that +stringWithContentsOfFile
returning nil is an error. The caller
Fred Kiefer wrote:
This is just one of the places where our current fontend backend
interface could need some improvements. My position here is that all the
PS interfaces to change any of the path drawing parameters should be
deprecated and NSBezierPath methods used instead (This does not
Serg Stoyan wrote:
Hi everybody,
Here is another improvement in appearance: NSScroller.
Fist patch changes drawing of knob slot of NSScroller (stiplled
instead of solid). Second one is updates NSBrowser according to NSScroller's changes.
I didn't apply this patch, mostly because I kind
Serg Stoyan wrote:
Hi,
Here is the minor changes, cleanups to NSBrowser against the latest CVS
(distance between columns and horizontal scroller was 1 pixel,
I applied this. Thanks.
--
Adam Fedor, Digital Optics Corp. | I'm glad I hate spinach, because
http://www.doc.com
Adam Fedor wrote:
Fred Kiefer wrote:
Fred Kiefer wrote:
BTW, this error message is shown eight times, when a NSSavePanel is
opened,
although only two columns are shown. I will inspect into this to find
out if there are unneeded operations going on.
After a bit of investigation I
Fred Kiefer wrote:
The gsave/grestore operations are rather expensive. Where possible we
should try to avoid them internally. Even without this there are
different ways we could achive the same results. This is one of the
Of course. It's certainly permissable for the path to just unset/reset
