wanted to add a little info to the description of this issue for clarity...
the schedule conflicts are showing up on the Q, not Google Calendar. it's on the Motorola Q that i am forced to manually update the available/busy flag any time an all day event is sync'ed to it. the flag itself is always being set to busy when syc'ing (regardless of direction), but Google doesn't really do much in the interface with regards to scheduling conflicts, so it doesn't really matter on that interface. depending on how your phone/mobile device handles/displays scheduling conflicts, this may not be that noticeable of a problem. -mike On Feb 12, 10:25 am, "MikeO" <[EMAIL PROTECTED]> wrote: > i posted a few months ago about this issue, but i think it got lost > amongst some other questions/issues i had posted, so i'm going to post > again... > > i am using free goosync with Google Domains and a Motorola Q. works > great for most everything; however, all items sync'ed are set as > "Busy", regardless of the actual setting (and regardless of the > direction of the sync). the problem is that certain events, > especially all day events, are not an indication in my schedule of > being busy, but they are showing up on my Q as having scheduling > conflicts (everything shows up in red, and there are conflict icons > all over the place). > > right now, i have to go in and manually change the flag after a sync. > then, if there are any changes to the event, the flag gets set back to > Busy when it's updated during the next sync (forcing me to have to > manually update it again). this is very cumbersome and distracting. > > so, every birthday, holiday, list of general to-do items that are not > time-specific, etc. that i put in as an all-day event in google > calendar causes a conflict across the entire day. ideally, the sync > would preserve the "available / busy" flag on events; but, as a > minimum, it would at least be improved if every "all day" event was > marked as available and every timed event was marked as busy (would > still be some incorrect events if done this way, but it would be > correct for a much larger percentage of sync'ed events). > > is this a known issue? does it affect others, or is it unique to > Google Domains and/or the Q? any chance this is something that is > going to be addressed in an upcoming (free or paid) release? > > this and the lack of scheduled/automatic sync are the two items that i > need to justify going to the paid service. don't know if any others > are in the same boat, but for me, the lack of these two features > severely limit the functionality. > > thanks for any info you can provide! > > -mike --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GooSync" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/goosync?hl=en -~----------~----~----~----~------~----~------~--~---
