To navigate the MiRow browser using the Apple Remote, you have to toggle between scroll mode and "mouse" mode. Mouse mode allows you to move the cursor around the screen (like you're using a mouse) using the Apple Remote. Holding the play/pause button activates and deactivates mouse mode in MiRow. Candelair seems to prevent this switch from occurring so you're always stuck in scroll and click mode. You can never get into mouse mode as long as Candelair is enabled.

Any chance this could be fixed? 

There's one detail worth knowing about Candelair's Legacy Mode, though: 
If you've enabled Candelair's Legacy Mode, you tell Candelair to behave like the OS X Leopard version of Apple's IR Controller driver (so that some old applications using Martin Kahr's broken Apple Remote code can still be used despite their unnecessary dependency on driver internals) - which includes the detail that OS X Leopard has no support for the "Play/Pause" button of the Aluminum Apple Remote. On OS X Leopard, the "Play/Pause" button of the Apple Remote is reported as "Select" button.

So, if you're using Candelair's Legacy Mode and an Aluminum Apple Remote, I recommend turning off Legacy Mode.

If you don't have Legacy Mode enabled, as their customer, please ask FireCore to look into the issue. Since Candelair creates and posts the exactly same events as Apple's own driver, I can't see any on Candelair's side. MiRow, on the other hand, is only possible by using lots and lots of private, undocumented APIs (Front Row has no official or publicly documented plugin support). FireCore is welcome to contact me with any technical questions regarding Candelair that they come up with while looking into the issue.

Best regards, 
Felix Schwarz 

Thanks for replying.

I actually posted this problem first in firecore's forums but never received a reply, so I then posted here.

I thought the "Legacy mode" was essential for computer running Snow Leopard because some Apple Remote/Front Row bugs appeared in Snow Leopard and were never fixed.

I've got one of the older white plastic Apple remotes and I'm wondering if something else is interfering with my remote. Rowmote works perfectly: scrolling is fast and clicking is responsive. With the plastic Apple Remote, I have to press slowly and deliberately and the remote will no longer scroll quickly through menu if I hold down the Up/Down buttons. I have to repeatedly click to get through long lists and it takes forever.

This problem, which started recently, occurs in XBMC, Plex, and Front Row, but only with the Apple Remote, not with Rowmote on my iPhone. 

The Legacy Mode is not related to this issue. It really is only there so you can continue to run old, unsupported software that uses Martin Kahr's driver internals dependent Apple Remote code, which has been broken once again by the new OS X Apple Remote driver in 10.6.2.

Today, however, pretty much every serious, supported application (including XBMC, Plex, Boxee, EyeTV, ..) using the Apple Remote uses my HIDRemote class - which doesn't have any such driver dependencies and therefore also doesn't need the Apple Remote driver to emulate the internals of old driver versions from previous OS versions.

Given your description, your problem probably is a battery that's about to run empty. In that case, the Apple Remote starts sending extra IR codes with every button press, which may explain your issues. Normally, OS X (or Remote Buddy) will inform you about a low battery. Since that battery warning, however, is also sent as a HID event, that HID event is only received by the application that currently uses the Apple Remote (and there usually can only be one at a time) and most applications don't implement any warning when receiving a low battery HID event, chances are you'll never see any warning come up.

My recommendation: try with a new battery.

Best regards, 
Felix Schwarz

P.S.: RowMote, just like Remote Buddy's AJAX Remote, uses Wi-Fi as its communication channel, which is far more reliable in transmitting information than the IR technology the Apple Remote uses. 

Thanks again for taking the time to answer my questions. It's much appreciated.