[missing-sync-winmobile-talk] Bugs? (or features?)

Pride Of Lions Nine Arts (LLC) prideoflions at gmail.com
Thu Oct 12 08:12:11 PDT 2006


Good Morning Brian.

Sorry if I was too cranky-sounding last night in the e-mail.  I had  
the Worst. Day. Evar!!!11!!1 and I typed that at the end of it all.   
So, all the snarkiness wasn't meant for you and your team of good- 
product-putting-out people.
K.
_____________________
Pride Of Lions Nine Arts, LLC
Location Sound Mixing/Recording for the Global Film/Video Community.

Kyiakhalid Ruiz, General Manager
P.O. Box 19164
Oakland, California 94619

(510) 813-3352 mob.
prideoflions at gmail.com
www.prideoflions.com (Coming Soon!)


On Oct 12, 2006, at 3:21, Brian M. Criscuolo wrote:

> Ah, yes. Your posting from the other day did not mention quitting  
> after disconnect, just "how nice it'd be to have the Missing Sync  
> disconnect when the device is taken from the cradle."
>
> I just poked through the code and have fixed this problem for a  
> future release. I tested it by clicking on the disconnect button as  
> well as pulling the device from the cradle.
>
> Thanks for the poke on that one!
>
> b
>
> On Oct 11, 2006, at 11:59 PM, Pride Of Lions Nine Arts (LLC) wrote:
>
>> Good Evening All.
>>
>> Brian, you and Ken need to co-ordinate your answers.  Here's what  
>> he said with regard to exiting the program by simply uncradling  
>> the Axim:
>>
>> "1)	I've noticed that it's difficult to reconnect the Axim to  
>> MissingSync after I disconnect the device.  I have it set to "Quit  
>> On Disconnect", but it won't recognize when I try to re-mount the  
>> device.  Do I always have to "Disconnect" the device from Windows  
>> Mobile before taking it out of the cradle, or can I have  
>> MissingSync set to disconnect on device removal and act as if I  
>> had chosen to disconnect it from within MissingSync?  It's neater  
>> and easier to not have to remember to remove it from MissingSync  
>> and just be able to remove the device when I need it.
>>>
>>
>> In the current release 2.5.1 and the 2.5.2 BETA the "Quit on  
>> Disconnect" only works if you disconnect by clicking on the red  
>> Disconnect button in the toolbar. I agree that it should  
>> disconnect and quit if you just pull the device from the cradle/ 
>> cable. We'll look at fixing that in a future release."
>>
>> So, maybe I'm not crazy and shouldn't have to trudge through  
>> support for something that isn't implemented yet.
>>
>> The advice about the "Activity Monitor" was spot on.  I "Force  
>> Quit" the offending services and they started right up again when  
>> I needed them.
>> K.
>>
>> _____________________
>> Pride Of Lions Nine Arts, LLC
>> Location Sound Mixing/Recording for the Global Film/Video Community.
>>
>> Kyiakhalid Ruiz, General Manager
>> P.O. Box 19164
>> Oakland, California 94619
>>
>> (510) 813-3352 mob.
>> prideoflions at gmail.com
>> www.prideoflions.com (Coming Soon!)
>>
>>
>> On Oct 10, 2006, at 5:18, Brian M. Criscuolo wrote:
>>
>>>
>>> On Oct 9, 2006, at 8:31 PM, Pride Of Lions Nine Arts (LLC) wrote:
>>>
>>>> We've talked before about how nice it'd be to have the Missing  
>>>> Sync disconnect when the device is taken from the cradle, but I  
>>>> have some new behaviors to report and get clarification on.
>>>>
>>>
>>> If you're connected, and turn off/unplug the device, we will  
>>> disconnect properly. If this isn't working for you please follow  
>>> up with support.
>>>
>>>> When the Missing Sync is "Disconnected" but the device is still  
>>>> in the cradle, how does one mount the device?  The buttons are  
>>>> grayed out, but it might be cool if it still "saw" the device  
>>>> and was ready to re-mount if the button were clicked.
>>>>
>>>
>>> You cannot mount the device at that time. The disconnect is more  
>>> than physical, it requires the ActiveSync application on the  
>>> device to be managing communication with the desktop. The easiest  
>>> thing is just to uncradle/recradle the device, or you can turn it  
>>> off, wait a few seconds, and turn it on.
>>>
>>>> I accidentally sent some files to the "Internal Storage" instead  
>>>> of the "CF Card" and stopped the process when I noticed it.  I  
>>>> then sent the files to the CF card and they went there fine, but  
>>>> now the "Sync" business is sketchy.  The Tasks haven't synced  
>>>> since yesterday at 5pm, and the Calendar and Contacts haven't  
>>>> synced since this morning at 7am.  Is there a setting I can set  
>>>> on either Missing Sync or the device (Axim x51v) or .Mac so that  
>>>> I can have my syncing back?  I tried a soft reset on the device,  
>>>> but haven't tried a restart on the Mac yet (I have a tedious  
>>>> process crunching away in the background and would hate to start  
>>>> it again.)
>>>>
>>>
>>> It sounds like the plugins might be in a state where they aren't  
>>> receiving messages from our application. Quit the Missing Sync  
>>> app, then launch Activity Monitor (Applications/Utilities) and  
>>> search all processes for "Mark/Space" - and then force quit those  
>>> that come up (you'll likely see the plugins). Then you can launch  
>>> the application again, connect up and go on your merry way.
>>>
>>> b
>>>
>>>> I know some of these have been talked about before I got the  
>>>> Axim and the new Mac, and I tried to follow some of these  
>>>> discussions, but they mean more now since I can actually play  
>>>> with the device and software in person.
>>>> K.


More information about the missing-sync-winmobile-talk mailing list