Have you considered using the Built-in Date.GMTOffset Property?
It has a slightly different Comment than r3 in the OLR.
Terry
On Oct 7, 2006, at 2:26 AM, Sven E Olsson wrote:
Hi,
I have now worked with RB2006R4-UB on OS X 10.4.8 Intel for two
days. I have done a lot of compiles and changes (both remove and
added code) in my app.
No crashes, and it just works fast, that before was extreme sluggish.
(I don't use plugins)
I also now get some feedbacks from my user, and it is very positive
feedbacks!
But I found some bugs in my own compiled app..
Console log errors, check it out:
http://www.realsoftware.com/feedback/viewreport.php?reportid=jovglwbu
I also found that a carbon call return wrong value when it is Intel
compiled:
<code>
// Code created by Mike Bailey <[EMAIL PROTECTED]>
// Added 12/30/2001 by Kevin Ballard
// 68k Compatible
#if TargetCarbon then
Declare Sub ReadLocation lib "Carbon" (location As ptr)
#else
Declare Sub ReadLocation lib "InterfaceLib" (location As ptr)
Inline68k("205F203C000C00E4A051")
#endif
Dim temp As MemoryBlock
Dim gmtOffset As Integer
temp = NewMemoryBlock(12)
ReadLocation temp
gmtOffset = temp.short(9) * 256 + temp.byte(11)
If (gmtOffset < 0) Then
gmtOffset = ceil(gmtOffset / 3600) * 100 + ((gmtOffset \ 60)
Mod 60)
Else
gmtOffset = floor(gmtOffset / 3600) * 100 + ((gmtOffset \ 60)
Mod 60)
End
Return gmtOffset
</code>
This generate 201 when the code is compiled to Intel and correct
200 when compiled to PPC, any ideas how to fix this?
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>