> On May 7, 2020, at 10:04 PM, Rob Petrovec wrote:
>
> Have you considered using a workspace to handle building all of your
> individual projects? That should solve your file path & linking problem.
>
Some of the dynamically linked libraries are large. If they are put in a
workspace with th
On May 8, 2020, at 09:08:17, Richard Charles via Cocoa-dev
wrote:
>
> Some of the dynamically linked libraries are large. If they are put in a
> workspace with the main project then it is so large it becomes cumbersome to
> work with.
>
> One library has over 1,100 source files. Using a works
Richard,
> On May 8, 2020, at 10:16, Steve Mills via Cocoa-dev
> wrote:
>
> On May 8, 2020, at 09:08:17, Richard Charles via Cocoa-dev
> wrote:
>>
>> Some of the dynamically linked libraries are large. If they are put in a
>> workspace with the main project then it is so large it becomes c
I have kind of a slide-show app.
Sometimes, when it switches from one image to the next, there is a noticeable
lag when the file size of the next image is very big, say, 50 MB or more.
Sometimes, it seems that loading the image takes 1-2 seconds.
So, I was thinking, maybe it helps to load the ne
iOS or MacOS?
> On May 8, 2020, at 11:53 AM, Gabriel Zachmann via Cocoa-dev
> wrote:
>
> I have kind of a slide-show app.
>
> Sometimes, when it switches from one image to the next, there is a noticeable
> lag when the file size of the next image is very big, say, 50 MB or more.
> Sometimes,
Thanks for the question: MacOS.
>
> iOS or MacOS?
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsub
What if you spawned another process (NSTask?) from the screensaver and tested
if a timer works in that? It’s hokey as hell, but I use this approach to
monitor a running process and do things when its state changes to suspended.
See if you can fire off a process and have a timer in it that logs
Oh Steve, which version of MacOS are you seeing this on?
> On May 4, 2020, at 8:33 AM, Steve Mills via Cocoa-dev
> wrote:
>
> On May 4, 2020, at 03:28:23, Gabriel Zachmann wrote:
>>
>> You mean, it could happen that Apple decides to make ScreenSaverView a
>> subclass of some class other th
Does this seem related?
https://9to5mac.com/2020/04/28/new-bug-found-in-macos-can-quickly-fill-up-storage-when-importing-photos-with-image-capture/
"The problem discovered by the NeoFinder team is that the Mac adds 1.5MB of
empty data to each converted photo, making the imported files larger fo
> On May 8, 2020, at 9:53 AM, Gabriel Zachmann via Cocoa-dev
> wrote:
>
> So, I was thinking, maybe it helps to load the next image concurrently, while
> the current one is still being displayed.
Sure. Just be aware that if you're using NSImage, simply loading an NSImage
does not rasterize
On May 8, 2020, at 12:50:23, Alex Zavatone wrote:
>
> Oh Steve, which version of MacOS are you seeing this on?
What? I'm not the OP of this thread.
--
Steve Mills
Drummer, Mac geek
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do
> On May 8, 2020, at 12:19 PM, Jens Alfke via Cocoa-dev
> wrote:
>
>
>
>> On May 8, 2020, at 9:53 AM, Gabriel Zachmann via Cocoa-dev
>> wrote:
>>
>> So, I was thinking, maybe it helps to load the next image concurrently,
>> while the current one is still being displayed.
>
> Sure. Just
> I also read about the GCD's dispatch queues, but it seems to me that this
would not be the suitable approach since I always only have one task
running concurrently to the main thread.
>
> Why not? Dispatch queues are always available. (The main thread is simply
> a special queue.) You can run th
> I second the use of GCD. Its also considerably simpler than NSThread,
> NSOperationQueue/NSOperation et al. This is the kind of operation that GCD
> was invented for.
Thanks a lot for your response(s).
To me a queue suggests that you have lots and lots of tasks arriving from the
produ
> Sure. Just be aware that if you're using NSImage, simply loading an NSImage
> does not rasterize it; the class tries to be 'lazy' about doing work. So your
> background task should explicitly render it, e.g. into an NSBitmapImageRep.
I am using CGImageSourceCreateImageAtIndex and related funct
> On May 8, 2020, at 15:13, Rob Petrovec via Cocoa-dev
> wrote:
>
>
>
>>> On May 8, 2020, at 12:19 PM, Jens Alfke via Cocoa-dev
>>> wrote:
>>>
>>>
>>>
On May 8, 2020, at 9:53 AM, Gabriel Zachmann via Cocoa-dev
wrote:
>>>
>>> So, I was thinking, maybe it helps to load the ne
Using a queue is part of GCD. You should probably not use the main queue since
that is analogous to the main thread and the main thread is meant for updating
the UI.
The good thing here is that you can sort of preload the next image in a queue
after your last one has displayed.
With a dispat
On May 8, 2020, at 6:00 PM, Gabriel Zachmann via Cocoa-dev
wrote:
>
>> Sure. Just be aware that if you're using NSImage, simply loading an NSImage
>> does not rasterize it; the class tries to be 'lazy' about doing work. So
>> your background task should explicitly render it, e.g. into an
>> N
18 matches
Mail list logo
