On Oct 19, 6:47 pm, Rob McBroom <[email protected]> wrote:
> On Oct 18, 2009, at 1:07 PM, Howard Melman wrote:
>
> > Are there known Trigger corruption issues with B56a7 or is this
> > likely just something on my machine?
>
> I feel like I've seen it discussed here, but I can't say for sure.
May be here:
http://u.nu/2vxj3
This (null) happens because QS fails to recover the command it
stored
in the Triggers.plist file, so it defaults to nil (and displays as
"(null)"). This is a side-effect of me trying to fix the issue
you've
mentioned, the inability to save certain kinds of triggers
(encapsulated commands, mainly).
On the corruption of the Triggers.plist file : I'm not sure it's
exact
to tell it like this. Most of the bug reports I've seen that show
this
are actually caused by the Trigger system failing to find the needed
class for a trigger type. This is a known issue, and should be
fixed.
To reproduce, install one of the plugins that add a trigger type
(Abracadabra, Mouse Corners, ...), create a trigger that use this
trigger type, then disable the plugin and restart. B54 should hang
with the now famous "Trigger.plist corruption problem" ;-), while
B56
shouldn't.
