|
Re: How to get full user name prior to 10.12?
The Foundation function NSFullUserName().
--
Shane Stanley <sstanley@...>
<www.macosxautomation.com/applescript/apps/>, <latenightsw.com>
The Foundation function NSFullUserName().
--
Shane Stanley <sstanley@...>
<www.macosxautomation.com/applescript/apps/>, <latenightsw.com>
|
By
Shane Stanley
·
#161
·
|
|
Re: How to get full user name prior to 10.12?
Ah, hidden in plain sight! Thanks
G.
Ah, hidden in plain sight! Thanks
G.
|
By
Graham Cox
·
#162
·
|
|
"broken pipe", but not when debugging...
Hi,
I’m using NSTask to ‘talk to’ a command line executable that is embedded in my app. I use NSPipe as its stdIn and stdOut channels.
When I run the code under Xcode, it works fine. When I
Hi,
I’m using NSTask to ‘talk to’ a command line executable that is embedded in my app. I use NSPipe as its stdIn and stdOut channels.
When I run the code under Xcode, it works fine. When I
|
By
Graham Cox
·
#163
·
|
|
Re: "broken pipe", but not when debugging...
For some reason lost in ancient Unix history, if you write to a file-descriptor that’s been closed at the other end, a SIGPIPE signal is raised. This will by default kill your process. It’s
For some reason lost in ancient Unix history, if you write to a file-descriptor that’s been closed at the other end, a SIGPIPE signal is raised. This will by default kill your process. It’s
|
By
Jens Alfke
·
#164
·
|
|
Re: "broken pipe", but not when debugging...
Before running your app open the Console app and put the process name of your app in the search bar. The run your app. I believe you'll see your output.
It seems with the new log system is you
Before running your app open the Console app and put the process name of your app in the search bar. The run your app. I believe you'll see your output.
It seems with the new log system is you
|
By
Marco S Hyman
·
#165
·
|
|
Re: "broken pipe", but not when debugging...
OK, makes (some) sense, thanks. I’m wondering why the file descriptor would be ‘closed at the other end’ though - does that mean one of us (the command line tool is not my code but I am
OK, makes (some) sense, thanks. I’m wondering why the file descriptor would be ‘closed at the other end’ though - does that mean one of us (the command line tool is not my code but I am
|
By
Graham Cox
·
#166
·
|
|
Re: "broken pipe", but not when debugging...
Well, this is so far a blind alley.
I can’t find any mention of functions called signal() or ioctl() in the current (Xcode 8) documentation browser. But then, it seems we’ve lost the ability to
Well, this is so far a blind alley.
I can’t find any mention of functions called signal() or ioctl() in the current (Xcode 8) documentation browser. But then, it seems we’ve lost the ability to
|
By
Graham Cox
·
#167
·
|
|
Re: "broken pipe", but not when debugging...
A broken pipe usually means that one end of the connection has been closed for one reason or another. You don’t show the actual
read and write code, but that is most likely where the problem occurs.
A broken pipe usually means that one end of the connection has been closed for one reason or another. You don’t show the actual
read and write code, but that is most likely where the problem occurs.
|
By
Jack Brindle
·
#168
·
|
|
Re: "broken pipe", but not when debugging...
Look at fcntl() (man fcntl). It has an operation parameter of F_SETNOSIGPIPE and F_GETNOSIGPIPE to manage the SIGPIPE signal handling on a file descriptor. Won’t find it in the Xcode
Look at fcntl() (man fcntl). It has an operation parameter of F_SETNOSIGPIPE and F_GETNOSIGPIPE to manage the SIGPIPE signal handling on a file descriptor. Won’t find it in the Xcode
|
By
Jonathan Prescott
·
#169
·
|
|
CGImage for writing large multi-page tiffs?
Hi all,
At the moment I am saving tiff files in a one-liner using [[myNSImage TIFFRepresentation] writeToFile:atomically:]. I am considering a change to write rather large multi-page tiff files
Hi all,
At the moment I am saving tiff files in a one-liner using [[myNSImage TIFFRepresentation] writeToFile:atomically:]. I am considering a change to write rather large multi-page tiff files
|
By
Jonathan Taylor
·
#170
·
|
|
(OT) Image Editing App for Mac?
Hi,
Can anyone recommend a light weight Image Creation and Editing App for the Mac?
I’d like to be able to create images with fixed dimensions and background colour and be able to resize
Hi,
Can anyone recommend a light weight Image Creation and Editing App for the Mac?
I’d like to be able to create images with fixed dimensions and background colour and be able to resize
|
By
Dave
·
#171
·
|
|
Re: (OT) Image Editing App for Mac?
How about Gimp?
By
Jim Adams
·
#172
·
|
|
Re: (OT) Image Editing App for Mac?
Um... I might just write code to do that. The 'hardest' thing is probably to get text positioning right.
For general image manipulation I use Pixelmator. I like it but I wouldn't exactly call it
Um... I might just write code to do that. The 'hardest' thing is probably to get text positioning right.
For general image manipulation I use Pixelmator. I like it but I wouldn't exactly call it
|
By
Andreas Mayer
·
#173
·
|
|
Re: (OT) Image Editing App for Mac?
Try canva.com. They have a reasonable free account for graphics editing online, apparently they have an iOS app too, although I've never tried that.
Sandor
Try canva.com. They have a reasonable free account for graphics editing online, apparently they have an iOS app too, although I've never tried that.
Sandor
|
By
Sandor Szatmari
·
#174
·
|
|
Re: (OT) Image Editing App for Mac?
I’ve been happy with Acorn for those purposes for years. The documentation is great too.
https://flyingmeat.com
Jim Crate
I’ve been happy with Acorn for those purposes for years. The documentation is great too.
https://flyingmeat.com
Jim Crate
|
By
Jim
·
#175
·
|
|
Re: "broken pipe", but not when debugging...
It does seem absurd that the most fundamental APIs — the C standard library and POSIX/Darwin system calls — aren’t supported by Xcode’s documentation features. Especially since the header
It does seem absurd that the most fundamental APIs — the C standard library and POSIX/Darwin system calls — aren’t supported by Xcode’s documentation features. Especially since the header
|
By
Jens Alfke
·
#176
·
|
|
Re: "broken pipe", but not when debugging...
Jens;
Thank you for the opportunity to expound on this. See below…
A look at the discussion for NSFileHandle’s writeData: method provides the following:
"This method raises an exception if the
Jens;
Thank you for the opportunity to expound on this. See below…
A look at the discussion for NSFileHandle’s writeData: method provides the following:
"This method raises an exception if the
|
By
Jack Brindle
·
#177
·
|
|
APFS & FileSystem attributes
Apologies if this is a dumb question, but I'm wondering whether we'll still be able to call NSFileManager api's like attributesOfItem and get back things like NSFileReferenceCount and the like.
Does
Apologies if this is a dumb question, but I'm wondering whether we'll still be able to call NSFileManager api's like attributesOfItem and get back things like NSFileReferenceCount and the like.
Does
|
By
2551phil
·
#178
·
|
|
Re: APFS & FileSystem attributes
If it did, it would break most apps, so no.
—Jens
If it did, it would break most apps, so no.
—Jens
|
By
Jens Alfke
·
#179
·
|
|
Re: APFS & FileSystem attributes
Breaking stuff isn’t always a red line for Apple, but from your reaction I’ll take it that there’d have been an righteous outcry by now were it the case.
I’ve had my head stuck in the sand as
Breaking stuff isn’t always a red line for Apple, but from your reaction I’ll take it that there’d have been an righteous outcry by now were it the case.
I’ve had my head stuck in the sand as
|
By
2551phil
·
#180
·
|