Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Catalog loaded bool #1216

Merged
merged 2 commits into from
Nov 28, 2012
Merged

Conversation

pjrobertson
Copy link
Member

I found this commit lying about in my branches (yes, somebody's been tidying up!)
83fab29f70117f70d226ce8b3b02d97b32ecf9ea

Not sure if it fixes a crash or something, but looks useful.
I also found a small optimisation commit somewhere, which didn't find its way into master, so it's here

Ensures that plugins do not try and write the catalog until it has been loaded
@skurfer
Copy link
Member

skurfer commented Nov 15, 2012

The plug-ins use QSLibrarian, so I'm worried about adding an iVar. I suppose adding it to the end is probably safe (vs. inserting it into the middle somewhere). Is that true?

@pjrobertson
Copy link
Member Author

Plugins don't subclass, so there shouldn't be a need to worry.

So I can stop you worrying:
https://groups.google.com/forum/?fromgroups=#!searchin/quicksilver---development/64$20bit$20class/quicksilver---development/k8afy9oaSo4/Xk6GfiLO05IJ

:D

On 15 November 2012 14:34, Rob McBroom notifications@github.com wrote:

The plug-ins use QSLibrarian, so I'm worried about adding an iVar. I
suppose adding it to the end is probably safe (vs. inserting it into the
middle somewhere). Is that true?


Reply to this email directly or view it on GitHubhttps://github.com//pull/1216#issuecomment-10410251.

@tiennou
Copy link
Member

tiennou commented Nov 15, 2012

If you feel really concerned about 32bit compatibility, put it in a static BOOL var. QSLibrarian is supposed to be a singleton, right ? ;-)

@pjrobertson
Copy link
Member Author

Hehe. You can tell that when I originally did this change (a year ago) I was concerned about 32bit compatibility (see the original commit here )
Now you can see I'm not ;-)

I'm happy to use a static as per 83fab29f70117f70d226ce8b3b02d97b32ecf9ea if it makes everyone happy.

@skurfer
Copy link
Member

skurfer commented Nov 16, 2012

OK, I had forgotten it only affected subclasses. So this should be fine. I'll test it out.

skurfer added a commit that referenced this pull request Nov 28, 2012
@skurfer skurfer merged commit 85d602f into quicksilver:master Nov 28, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants