View Full Version : Severe iCal Bug!
Evergreen
Nov 9, 2003, 06:22 AM
iCal does not go to B.C.! Even worse it does not go beyond 2851612 A.D.!!
How do I make a calendar entry for a B.C. date?!
What happens in the year 2851613, are we supposed to stop using Apple's iCal in favor of another product!?!!????:confused:
Evergreen
Nov 9, 2003, 06:23 AM
Also, this is build 616.
5300cs
Nov 9, 2003, 07:32 AM
um... . .. . . . ... are you serious about this?
yamabushi
Nov 9, 2003, 07:51 AM
That darn Y2.8Mil bug. Better start stocking up on food and water for your shelter now, before the blackouts and riots. ;) Nah, as long as you bought your portable fusion power generator and food replicator recently I think you should be alright. :) Or maybe Apple will just be kind enough to release an update to iCal before then.
Powerbook G5
Nov 9, 2003, 09:30 AM
Originally posted by Evergreen
Also, this is build 616.
I thought 616 was an inaccurate number for the antichrist due to the problem of translating it out of its original language in order to force Nero Caesar into being fit into the role. I believe that is what you are getting at with it being build 616?
johnnyjibbs
Nov 9, 2003, 02:02 PM
On a related note, I really hate the new info drawer on iCal 1.5.1. iCal is an app that needs to viewed full screen (I have a 12" PB) and I couldn't for the life of me find the info palette for ages, before realising that the new drawer panel was sliding in and out off the edge of the screen. Now I have to resize iCal so it's only using half the screen so that I can view the info drawer when I need to. Annoying and an utterly pointless addition. I want iCal 1.0.2 back...
backspinner
Nov 9, 2003, 03:02 PM
Originally posted by johnnyjibbs
On a related note
They should simply place the labels above the data in the drawer, then it could be half as wide without loosing functionality.
Maybe somebody can tweak this in project builder?
Evergreen
Nov 9, 2003, 05:59 PM
Ok seriously, why stop at January 2.8m? Could Steve be making a prediction?
Horrortaxi
Nov 9, 2003, 06:52 PM
By then I think your Mac will be obsolete so I wouldn't worry about it. Just to be sure you should have it email you a reminder a few days before it runs out so that you'll remember to buy a new calender.
bennetsaysargh
Nov 9, 2003, 07:05 PM
Originally posted by Evergreen
Ok seriously, why stop at January 2.8m? Could Steve be making a prediction?
he is the new oracle! or maybe that is the day apple will cease to exist? they merge with MS? they become world leaders?
who knows?:confused:
Powerbook G5
Nov 9, 2003, 08:15 PM
By then we might have OS 11 with iCal 2.0!
jxyama
Nov 9, 2003, 09:04 PM
i'm sure the year 2.8m is the upper limit of how many ever bytes iCal uses for the date. nothing deep...
if you have a PDA, try checking the upper limit on the date. it'll be less than 2.8M AD for sure.
mikeyredk
Nov 9, 2003, 09:36 PM
speaking about time limits
the clock in panther doesn't go past 2037
Evergreen
Nov 9, 2003, 11:45 PM
Originally posted by jxyama
if you have a PDA, try checking the upper limit on the date. it'll be less than 2.8M AD for sure. iCal for PDA?
benixau
Nov 10, 2003, 01:47 AM
Originally posted by Powerbook G5
By then we might have OS 11 with iCal 2.0!
Ha Ha Ha Ha Ha
He He He He He
Ha Ha Ha Ha Ha
That's a good one. Really - OS11 - Ha.
Man - like we would ever get to OS11 - we are stil going to be on OS10.xx.xx by then
macguymike
Nov 10, 2003, 03:35 AM
Originally posted by johnnyjibbs
On a related note, I really hate the new info drawer on iCal 1.5.1.
I've posted about this before. You're definitely not alone, here.
Who did the beta testing on the 12" laptops for iCal and why did they give it the okay? It's terrible. :rolleyes: :p
HasanDaddy
Nov 10, 2003, 04:45 AM
what the hell are you guys planning within your iCals???
your future marriage
future divorce
followed by your next re-marriage
???
LimeLite
Nov 10, 2003, 05:12 AM
Originally posted by mikeyredk
speaking about time limits
the clock in panther doesn't go past 2037
Does it really need to? The Macintosh isn't even 20 years old yet, and obviously no one is actively using the operating system that came with that one. Imagine 10 years from now. In 2037, or about 34 years from now (since it would be able to go through 2037, not just up to it) I'm sure that Panther will be perceived as extremely obsolete.
On an interesting note, Jaguar lets you go well past 3000. I got bored holding down the button, so not sure where Jags limits are.
Horrortaxi
Nov 10, 2003, 09:21 AM
Originally posted by HasanDaddy
what the hell are you guys planning within your iCals???
Since he's looking for the year 2851612 he must be planning evolution of various species.
What if Nostradamus had published an iCal for us all to look at?
mrjamin
Nov 10, 2003, 08:01 PM
another major bug i've come accross is that when i sync it with my toaster with iSync, my toast burns.
mrjamin
Nov 10, 2003, 08:12 PM
Originally posted by mikeyredk
speaking about time limits
the clock in panther doesn't go past 2037
That'll be something to do with the unix core of OSX as 2000000000 seconds since the unix epoch falls in the year 2037.
Makosuke
Nov 10, 2003, 08:38 PM
Originally posted by HasanDaddy
what the hell are you guys planning within your iCals???Duh... the sun going nova. I mean, I'd like an automated warning a little while before that happens, so I can start working on a colony ship to get off this rock before it's vaporized.
Man... 2.8 million years. You can barely plan ahead for evolutionary changes with that. Gonna need at least a few more billion before the thing is of any real use at all.
bennetsaysargh
Nov 10, 2003, 08:57 PM
Originally posted by mrjamin
another major bug i've come accross is that when i sync it with my toaster with iSync, my toast burns.
:eek: me too! also when i try and sync with my toilet, it bursts into flames.
seriously, i thin we don't have to worry about going past 2.8 million. perhaps BC could be put in because of historical purposes? schools studying, maybe?
vBulletin® v3.8.6, Copyright ©2000-2012, Jelsoft Enterprises Ltd.