The idea is good but I can't try that as many of my events are with invittee. 
If I delete & add then I won't get invittee added.



Vishal Sheth

-- Sent from my Palm Pre
George Kontos wrote:


 



  


    
      
      
      
OK, I did this scientifically and took precise measurements.  Most of my

calendar events open in 1 - 2 seconds.  Events that have repeats or alarm

take longer to open, 3 - 4 seconds.  One specific problematic one (repeats

weekdays + alarm) took between 9 - 12 seconds to open.  (Note that by "open"

I mean open the dialogu box and fully populate all the fields so you can

edit them.  All my events *start* to open instantly, but it can take up to

12 seconds for all the data in the fields to appear.)  



Solution:  I had two events that were really slow-to-open.  I deleted them

and re-created them from scratch on the Pre.  Now they open in 1 - 2

seconds.  I noticed the problematic ones are all carry-overs from my old

Treo 700p running DateBk6.  DateBk6 always inserted embedded/hidden codes in

the notes section of calendar events.  Maybe that's what was hosing some of

my events.  



George



-----Original Message-----

From: Don Ferguson

Sent: Friday, February 12, 2010 3:15 PM

To: Treo List Yahoo

Subject: RE: [Treo] Pre calendar is S L O W



Nope, that's not normal.  Not even close to that much time.  Calendar isn't

as fast as it should be, but it's much faster with 1.3.5.1 than previously.

10 seconds to open a calendar entry is a problem.  On mine it takes a split

second.



Cheers,

Don



From: George Kontos

Sent: Friday, February 12, 2010 8:14 AM

To: Treo List Yahoo

Subject: [Treo] Pre calendar is S L O W



Have you guys noticed this? 



When I open an event from the calendar, it sometimes takes about 10 seconds

or more for the event details to fully load. And sometimes when I go to

delete an event, when I hit the delete button, the calendar hangs/freezes

right there at the drop down menu, and won't recover. I have to swipe away

the app and start over. Today I realized this was happening when I hit the

delete button too quickly, BEFORE the event details have fully loaded. If I

wait patiently and then hit delete, it doesn't freeze up. 



George





    
     

    
    






  









[Non-text portions of this message have been removed]

Reply via email to