On Jun 11, 2014, at 8:01 PM, Devarshi Kulshreshtha
devarshi.bluec...@gmail.com wrote:
Because of all the problems I faced I finally decided to use a third
party library - Chilkat
I’m skeptical of using any non-open-source crypto code, since there’s no way to
do peer review on it, and that
Can¹t seem to get this to work. I have a collection view in a popover
(dismissed with a ³close² button) launched from a sheet. Delegate is set to
controller which declares NSCollectionViewDelegate, implements the validate
and accept drop protocols. Collection view (not the enclosing scroll view)
On Jun 11, 2014, at 6:46 PM, KappA rejek...@gmail.com wrote:
For some reason it doesn't like the below - you need to comment that out, and
uncheck that option in IB:
self.textView.layoutManager.allowsNonContiguousLayout = YES;
At least that's how I fixed it :) Not sure why it doesn't
On Thu, Jun 12, 2014, at 10:21 AM, Seth Willits wrote:
On Jun 11, 2014, at 6:46 PM, KappA rejek...@gmail.com wrote:
For some reason it doesn't like the below - you need to comment that out,
and uncheck that option in IB:
self.textView.layoutManager.allowsNonContiguousLayout = YES;
On Jun 12, 2014, at 11:25 AM, Kyle Sluder k...@ksluder.com wrote:
For some reason it doesn't like the below - you need to comment that out,
and uncheck that option in IB:
self.textView.layoutManager.allowsNonContiguousLayout = YES;
At least that's how I fixed it :) Not sure why it
That's exactly what I said.
Not sure why it doesn't like that property when using IB.
To me, that setting took your broken and hung app and made it work just as
your fast one. I'll leave the rest up to you to figure out why. And if you
read the docs about that setting, it seems to be giving you
On Jun 12, 2014, at 11:49 AM, Seth Willits sli...@araelium.com wrote:
On Jun 12, 2014, at 11:25 AM, Kyle Sluder k...@ksluder.com wrote:
For some reason it doesn't like the below - you need to comment that out,
and uncheck that option in IB:
I need to do some more testing, but I may have a workaround for my problem.
Instead of opening the document via NSDocumentController, ask NSWorkspace to
open the file in my app instead
I spoke too soon. Reopening the document via NSWorkspace also has the same
problem: the sandbox will
I don’t know whether this is relevant to your issue, but for what it’s worth,
(a) I have had a problem with OS X mysteriously locking files as result of the
file being set to user immutable”, and (b) I know that the autosave
functionality in NSDocument interacts with the immutable setting.
In
On Wed, 11 Jun 2014 20:38:34 -0700, Cosmo said:
Is it just me, or is there something broken with debugging Swift in the
Xcode 6 beta? I am running into problems like: local variables that are
within scope not appearing in the debugger’s variables list; values for
string variables not being
On Tue, 10 Jun 2014 08:38:10 -0700, Seth Willits said:
If that's really how it works, then UTIs are really seriously stupidly
broken in this kind of case, and I just can't believe that's true.
Believe it. :)
The only real option I see is to not use UTIs at all.
Exactly. It's only really safe
On Jun 11, 2014, at 11:38 PM, Cosmo minonom...@gmail.com wrote:
Is it just me, or is there something broken with debugging Swift in the Xcode
6 beta? I am running into problems like: local variables that are within
scope not appearing in the debugger’s variables list; values for string
On Jun 12, 2014, at 4:53 PM, SevenBits wrote:
On Jun 11, 2014, at 11:38 PM, Cosmo minonom...@gmail.com wrote:
Is it just me, or is there something broken with debugging Swift in the
Xcode 6 beta? I am running into problems like: local variables that are
within scope not appearing in the
On Thu, 12 Jun 2014 16:59:25 -0400, Alex Zavatone said:
Don’t be so harsh. Jeez, it’s not like Xcode 6 is beta software or
anything crazy like that…
Aren't these the exact issues we are supposed to point out in a Beta?
At least they were the last time I ran a beta program for an IDE.
Yes,
I don’t know whether this is relevant to your issue, but for what it’s worth,
(a) I have had a problem with OS X mysteriously locking files as result of
the file being set to user immutable”, and (b) I know that the autosave
functionality in NSDocument interacts with the immutable setting.
Hello,
I need to develop a tool which processes stdin as it arrives from its parent
process. The following code works as expected when it is in invoked with no
stdin, that is…
Air2:Debug jk$ ./MyTool
But if I pipe some initial stdin to it, like this
Air2:Debug jk$ echo Hello | ./MyTool
On Jun 12, 2014, at 3:24 PM, Jerry Krinock je...@ieee.org wrote:
I need to develop a tool which processes stdin as it arrives from its parent
process. The following code works as expected when it is in invoked with no
stdin, that is…
Air2:Debug jk$ ./MyTool
But if I pipe some initial
On 2014 Jun 12, at 15:35, Greg Parker gpar...@apple.com wrote:
If you get back an empty data object you are at end of file, and you should
not call -waitForDataInBackgroundAndNotify again.
Thank you, Greg. I thought that same thing a couple hours ago. But it trades
one problem for
On Jun 12, 2014, at 4:53 PM, Jerry Krinock je...@ieee.org wrote:
On 2014 Jun 12, at 15:35, Greg Parker gpar...@apple.com wrote:
If you get back an empty data object you are at end of file, and you should
not call -waitForDataInBackgroundAndNotify again.
Thank you, Greg. I thought that same
On 2014 Jun 12, at 17:12, Greg Parker gpar...@apple.com wrote:
This sends text via stdin, then closes stdin. Nothing the user types will
appear on stdin.
echo text | ./YourTool
I see. Then the revised code is behaving correctly, so I should move on. Have
a good evening, Greg!
On Jun 12, 2014, at 5:43 PM, Jerry Krinock je...@ieee.org wrote:
On 2014 Jun 12, at 17:12, Greg Parker gpar...@apple.com wrote:
This sends text via stdin, then closes stdin. Nothing the user types will
appear on stdin.
echo text | ./YourTool
I see. Then the revised code is behaving
21 matches
Mail list logo
