Skip to content

Loading…

"Attached Firewire Device" evidence source no longer available? #312

Open
krissp opened this Issue · 9 comments

2 participants

@krissp

It appears this feature has disappeared in a recent build of ControlPlane.

@dustinrue
Owner

What model Mac do you have and does have a built in FireWire interface?

@krissp

It's a 2012 MacBook Air, so no, it doesn't have a built in FireWire interface.
I use the Thunderbolt to FireWire Adapter though, and that worked with a prior version of Control Plane (can't say for sure which version changed this).

So is it basically just hiding the FireWire evidence source because there's no built-in interface?

@dustinrue
Owner

Yes and I do that when controlplane loads so if you plug in the adapter after the fact it won't then enable the evidence source. I'll look into it a bit

@krissp

Thanks

@krissp

Thank you! Yes, the FireWire evidence source is now working for me with the Thunderbolt adapter.

Just one small note - I noticed that if I launch this new build but have no context with a strong enough confidence level to cause a switch (so it's in the default context), the Active Context is displayed as '?'. Screenshot attached. I'm not sure if this is intentional, but the 1.4.0 release of ControlPlane displays the name of my default context. This is obviously not much of an issue, and it doesn't appear to be a problem functionally, but I'm just pointing it out in case it's related to the FireWire changes.

screen shot 2014-03-15 at 7 18 36 pm

@dustinrue
Owner

Have you enabled the multiple active contexts option? Just helps me debug the issue is all.

@krissp

No, I have not enabled multiple active contexts.

I see that it's actually now displaying '?' at launch regardless of the context I am in, so it's not limited to the default context. It changes to display a name after the first triggered rule.

But anyway, I think I isolated it to the "Restore previous context when ControlPlane starts" option. If I uncheck that, then it's fine.

@dustinrue
Owner

Perfect, thanks for the feedback. The issue is most likely a result of some code shuffling to allow the multiple active contexts to work at all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.