Authors CurseForge

it does update the kernel ;)

wxWidgets actually, but yeah that one.

Any news on the new Mac client?

In general I'm still very pleased with the new client, but the "Scanning addon directories" hourly system slowdown is really starting to get to me. I have a fairly fast machine, but it still takes over a minute, makes my interface nearly unusable, and seems to happen "all the time." Any chance we could get an option to disable it, or at least have it only occur on startup? I think the case of "manually installed a bunch of addons and didn't tell the updater between reboots" is fairly rare...

.18 should be much faster than previous versions, also the mac client is progressing nicely I'll probably have an alpha out next week.

It is faster, I did notice that today, but I still have to look at that annoying little box every hour :) It took a long time, but it's really gotten to me...things living in the systray shouldn't pop up boxes that don't require user input, IMHO.

Quote from specific

It is faster, I did notice that today, but I still have to look at that annoying little box every hour :) It took a long time, but it's really gotten to me...things living in the systray shouldn't pop up boxes that don't require user input, IMHO.

Agreed. From a design perspective, if it is important to indicate a periodic activity, a subtle change or animation of the tray icon is sufficient. Whether or not scanning local directories is an important enough periodic activity the user needs to be aware of is something the developers should decide. (I could live happily without any icon change or animation at all, for example.)

If this periodic activity could cause a noticable disruption in system performance for a duration long enough for the user to react to, I'd say that periodic activity is important. That activity should be then cancellable by the user right clicking on the tray icon. (Again, personally, I have not found scanning in RC1 to be disruptive at all. If I happen to be paying attention, the progress bar is usually gone before I'd even get a chance to click it.)

If the periodic activity has resulted in a status the user should be made aware of (e.g., updates are available, unidentifiable addon requires user intervention, a plauge of locusts is about to swarm, etc.), this is the point at which a pop-up notification would be warranted.

Edit: I should mention that the scanning progress bar may still provide important information for testing purposes in beta versions of the client, but provide little useful or actionable information in the released version of the client. My comments were based on the fact that the client is labeled as RC (release candidate). No extra debugging, logging, or profiling features should be enabled in these builds.

Hi,

with the new client being able to install libraries seperately i have encountered a few packages where the author did not set them up properly. The *-nolib packages are missing the required libraries which do not have a standalone version.

At the moment i need to flag the package as ignored and install the complete package by hand. The client clearly states that separate library installs are optional and not supported by all authors.

Would it be possible to flag the packages that do not work as no-lib on the homepage so the C-Client can install the full package instead ? (and maybe notify the author that his meta information is wrong)