Date & Timer:  BUG????

Description of what I need to do:   Track time from a timestamp sent as a value in a service.
Description of how it is done:
1.  create a new date object from the values sent in the service.
2.  create a timer that tracks seconds
3.  every 60 seconds increase the value of the date object by one minute
PROBLEM:
If someone changes the TIME ZONE  properties in Windows the value of the time in the flex app is also updated, which makes no sense because the variable that holds the current time should be completely independent of the machine's date/time properties. This does not happen if the hour/minutes Windows properties are changed, only when the time zone is changed, which is too strange.
The application is a time clock for employees to clock in and out  and so must not be open to manipulation.
WHY???  Is it something to do with the Timer class?  What is the relationship of the flex app Date Object /Timer Class to the date/time properties of the local machine?  Or, am I totally missing something.
I haven't included my code because its pretty mundane stuff but can if someone thinks it will help.
Thanks -- if anyone understands how this works.

Post an example.

Similar Messages

  • Another Date/Time Bug?

    I found now, that all my images from 10D and G2 have a wrong Date/Time Original in lightroom. It's shown one hour too early. All my other viewers show the correct time in exif data.
    The images from my 30D otherwise are correct in lightroom.
    What happens here?
    Juergen

    Ok, I looked a little bit deeper.
    All my pictures from end of october until end of march have correct time in lightroom. Daylight saving time begins last weekend of march and ends last weekend of october in germany.
    But I always change the time in my cameras on the first day after daylight saving time changes. It seems it hasn't anything to do with the camera model because I own the 30D only since last november.
    Why doesn't lightroom only show the exif times from the files and is calculating something wrong by itself?
    Juergen

  • Time and date reset bug

    hu guys, recently ive been experiencing a time and date reset bug, sometimes when i open up my computer it says something like your date is set to (i forgot the exact date but the year is 2001) so i change it back to the correct time and date, im not sure how i got the bug, can anyone help me fix this problem, its beginning to be annoying. thanks in advance!!

    Sherwin,
    Those symptoms indicate that you need to get your backup (PRAM) battery replaced.If your computer does not retain parameter RAM (PRAM) settings when it is turned off, this generally indicates that the battery needs to be changed.;~)

  • Day of year bug - format date/time string and scan from string?

    I've noticed that the day of year returned by "Format Date/Time String.vi" starts with a value of 1 for Jan-1 while "Scan from String.vi" wants a 0 index.  Is this a bug or feature?  
    (I'm using Labview 2010 Service Pack 1)

    I think the best idea is to use seconds since for your arithmetic, because it is going to be the most consistent and robust solution. Knowing that a day has 86400 seconds is all that is needed and you won't run in possible inconsistencies with date time implementations caused by our anything but logic calender. I would hazard that the functionality of converting a timestamp into year and day of year and back is impossible to make consistent without sacrificing other possibly conflicting transformation in the Timestamp into String and Timestamp from String manipulations.
    "Seconds since" being the actual base unit in all LabVIEW timestamps, it is best to do any arithmetic on it in this base unit.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • BUG: LR 2.1 adjusts date/time back 1 hour

    I'm really really annoyed. When I import images into LR 2.1, it changes the date/time of the image back by 1 hour - I assume its changing to standard time from daylight savings time. Why is this done? There doesn't seem to be a configuration option for this.

    "CR Henderson - 4:40pm Nov 23, 08 PST (#35 of 35)
    A work around that I have used since LR 1.0:
    1. Set camera time to GMT and leave it there.
    2. Take pictures and download them to PC hard drive.
    3. Convert to .DNG using DNG Converter
    4. Run ExifTool GUI on files and use XMP: DateTime copy from EXIF
    5. Import into LR
    #4 sets the XMP time to the EXIF time and removes the time zone offset, i.e. the XMP time is set to be the EXIF time with zero offset and since that is what I have my cameras set to things work out well. With the XMP time already set LR doesn't mess with it (or at least versions 1x-2.1 haven't).
    It is possible the above will work for other RAW files supported by ExifTool GUI. I know it does with the Canon CR2 files I use (30D, 40D)."
    Personally, having paid for the software, (it isn't freeware) I would like a FIX rather than a workaround. A little response from Adobe as to when it will be fixed would be appreciated, if it is not too much trouble?
    The last Date / Time issue required purchase of a new version, I hope this will not be a trend in LR. As others have pointed out just writing and reading the EXIF time is not rocket science. It is just a matter of trying to get the LR programmers to leave it alone (since the beta!) and not keep messing around with it. There has never been any explanation of what they were attempting to accomplish by modifying EXIF Date / Time?

  • Date Time Original & Date Time Digitized bug

    I have noticed that in Lightroom (1.1 or 1.2, doesn't matter) my photographs display WRONG Date Time Original & Date Time Digitized in the Metadata section. Both are exactly 30 minutes behind the actual time the photos were shot - eg., if I have shot a photo at 7:00pm, it will be shown as though it was shot at 6:30pm. Bridge correctly displays both this info. Any suggestions on how to rectify this info in Lightroom? Thanks,

    If you are shooting RAW, take care with "Edit capture time". There is
    evidence that it causes a rewrite of the RAW file by LR. This
    kind of a rewrite is dangerous, sometimes causing corruption. See
    this thread for a discussion:
    http://www.adobeforums.com/webx/.3c0331a6
    --Milt--

  • DID YOU KNOW?? - ABOUT DATE TIME CONVERTERS??

    Hi All,
    DID YOU KNOW??
    That the Creator IDE provides a set of converters that you can use to convert component data. If your input field is for numbers, then you most likely need a converter. Converters are also good for formatting dates, times, and currency values. The standard converters, which you can use are located in the Converters section of the Components Palette.
    The Date Time Converter
    A Date Time Converter Converts between java.lang.String values in your component properties and data types of java.util.Date. The conversion usually applies to the property of a component used to display values and to pick up values entered by users, such as the text property of a Text Field component.
    An example is binding a JavaServer Faces component to to a database column of type DATE. When you bind a component, the IDE normally identifies the data type for you and sets the appropriate converter when you establish a binding to the value property. However, you can also add this converter manually by setting the component's converter property.
    * Note: If you are using an Oracle database, use the SQL Timestamp converter instead.
    Learn more :-
    JDBC Type Conversions
    http://developers.sun.com/prodtech/javatools/jscreator/reference/docs/help/2update1/connect_data/jdbc_type_conversions.html
    Using Converters
    http://developers.sun.com/prodtech/javatools/jscreator/learning/tutorials/2/converters.html
    We would like to know the following from you :-
    1) Why and How are you using Converters in applications you are building?
    2) Did you face any challenges while using them?
    3) Did you find any cool ways of using these or build any cool custom converters?
    4) Any feedback you might want to share about converters to make it easier in using them.
    Thanks for all your inputs and for joining in the discussion.
    K

    did you know that sqlTimestamp converter returns value of java.sql.Date type if you are using sun's oracle jdbc driver. It will return the correct type if you use oracle's jdbc driver. Not sure why this happen, though. Bug?

  • WARNING: Adjust Date & Time doesn't work

    I bought Aperture 2.0 because I was thrilled they finally have an adjust date/time feature. The interface is great, but it simply doesn't work.
    I was trying to adjust a batch of images by 30 seconds to get it in sync with another camera, however, it ended up adjusting it by 30 minutes!
    I was trying to get the time to change from:
    1:33:09 PM to
    1:32:39 PM
    and the image ended up at
    1:00:33 PM
    Anyone else had a similar problem or a solution for this serious bug?

    I added my own topic earlier this morning. In my case, it's working just fine if my primary image is RAW and all selected images are also RAW (Canon 300D). It also works just fine if the primary and all selected images are JPEG (from either a Canon S3 or a Panasonic Lumix digicam). However, if the primary image is RAW (Canon 300D) and any selected images are JPEG (anything modified in iPhoto, or originally shot in JPEG from by Canon 300D), all **** breaks loose on those JPEG image dates.
    I have some which went back a few months, but most of them jumped forward between 6 months and 2 years.
    Again, something is severely broken with this function.
    Anyone know how to get the original dates back? Please? I'm setting aside several hours tonight to restore the pre-2.0 backup, export my 2.0-only projects, and import those back in, just forgetting any changes I'd made to historical project files in the meantime. This really *****.

  • Yahoo email - Updated date/time stuck

    Odd one...
    for starters, Yahoo push does not work at all for me... no big deal though, I just check it periodically..
    Here is the odd part.
    Since Monday, when I check my mail, it does receive mail, however, when I look at the time at the bottom for last updated, it is stuck at 7/16/07 3:04pm
    I have deleted the account and readded it, I have reset the iphone, and I have cleared out the yahoo inbox... no matter what I do, the 'Last Updated' date & time is stuck at the above, which is quite annoying.
    This only occurs in that Yahoo account. Gmail and POP work fine.
    I assume this is a bug, but has anyone else experienced this?

    I gave up on Yahoo. Gmail has been working pretty good for me on the iPhone. Very reliable, I can use my work email ID as a reply-to, doesnt care if its Wifi or EDGE, and the spam filters are top notch. Its free with no advertising (except from happy users like me )

  • Date Time in Coldfusion at Daylight Saving

    Hi
    In coldfusion, I have problem creating Date Time using CreateDateTime when the daylight saving switch. For example
    CreateDateTime(2011,3,13,2,0,0) gives error.
    Also if you do like this
    DateAdd('h',1,CreateDateTime(2011,3,13,1,0,0)) gives "2011,3,13,3,0,0" ie instead of 2AM it returns 3AM. This is happening every daylight saving switch time.
    This is a bug in coldfusion?
    It should be fixed by Coldfusion.
    Thanks

    On 3/17/2011 12:39 AM, Paresh_Patel said:
    >
    When we loop through the 24 hours on daylight saving day e.g
    >
    <cfset startDate = CreateDateTime(2011,3,13,0,0,0)>
    >
    <cfoutput>
    <cfloop from="1" to="22" index="dayNo">
          <cfset startDate = dateAdd('h', 1, startDate)>
          #hour(startDate)#<br>
    </cfloop>
    </cfoutput>
    >
    This will show wrong hours (2 is missing)
    and that means you've fallen into timezone hell.

  • Getting correct Date/Time data in DIAdem 11 from LabView tdms data

    I've got a handful of large tdms  files (9-18 million data points) collected with LabView that I need to extract elements of, and export as a text file, with the time data as a string.
    I'm using DataFileLoadSelect and the Register option and then DataBlCopy to bring in a chunk of data at a time, but I'm having to explicitly convert each time value from a LabView timebase (1/1/1904) to the DIAdem timebase (1/1/0000), not to mention the offset,  before writing the date-time as a text string - this really slows the process down. 
    I't strikes me that DIAdem(11.1) has got to have a way to read LabView timestamps correctly, but I'm a DIAdem novice, so any suggestions would be helpful. And no, I don't have LabView installed locally, so using a LabView vi is not an option for me.
    Thanks,
    Eric
    Solved!
    Go to Solution.

    WfmToDateWfm works great, but there is a bug in the code if you want to use DataFileLoadRed and your starting point is not at the beginning of the file.  There is a provision in WfmToDateWfm to handle the offset, but it's not hooked up:
    OffStartTime = ChnPropValGet(Channel, "wf_start_offset") ChnDeltaTime = ChnPropValGet(Channel, "wf_increment")
    RelStartTime = 24*3600*(Trunc(ChnStartTime) + 693958 + Abs(Frac(ChnStartTime)))
    To make WfmToDateWfm work with an offset, simly add the variable OffStartTime to the RHS of RelStartTime
    Eric 

  • Date Time issue factory unlocked iphone 4s

    I have a factory unlocked iphone 4s bought in Apple store US and currently in India. In Settings -> General -> Date & Time, I am setting "on" Set Automatically. After some time say 2-3 hours, the time automatically moves back by 30 minutes. In India there is no daylight savings. I am forced to set "off" for the "Set Automatically" option and then choose the timezone, time to keep it to the correct time. Anyone facing this issue ? By setting it to "Set Automatically" on, my understanding is it should sync with the mobile provider ("Airtel"). Is this a bug in iOS ?

    i have same problem i also went to apple store but the can not find any problem i don't know what to do ?
    i hop it's just a sofware problem

  • How do I preserve date/time when converting to DNG?

    When I convert a file to DNG format in Lightroom, it changes the capture time in the metadata to the current date and time, rather than copying the source data.  Is there a way in which I can tell it to leave my dates alone?

    You wrote: “I noticed my mistake. It seems that what the conversion process was changing was the ‘Metadata Date’ and ‘Date Time’ fields, but ‘Date Time ‘" and ‘Date Time Digitized’ were remaining the proper, original date. The cause of my confusion was that my Metadata panel view was hiding all but the ‘Date Time’ field, so it appeared as though it had overwritten my prior date information.”
    Date/times in photo metadata can be very confusing.  There are all these fields with confusing names imposed by legacy industry standards -- I challenge anyone except a metadata nerd like me to remember the meanings and differences of Date/Time, Date/Time Original, Date/Time Digitized, Capture Time, Metadata Date, Modify Date, ....  The worst are the two XMP fields Date Created and Create Date, which have two very different meanings!  And every app and operating system makes a half-hearted attempt to "simplify" it for the user by choosing different names.   
    LR makes no serious attempt to make this easy for the user, and over the first several versions, it's handling of date/times was pretty sloppy. (It still has outstanding bugs that don't crop up that often in practice.)  You would think that at least LR would provide roll-over tool tips on the field names in the Metadata panel explaining each field.

  • Date Time Original different in Lightroom and Bridge

    Why is it that the Date Time Original in Lightroom is affected by whatever time zone the PC is set to? This is not the case in Bridge.
    Example:
    I fly from San Francisco to Washington DC and set my notebook's time zone from Pacific Time to Eastern Time upon arrival. I also make the necessary adjustment to the Time on my camera. I shoot a photo at 6pm in Washington DC, upload it to my notebook and import it into Lightroom. Lightroom shows a Date Time Original of 6pm. So does Bridge. So far so good.
    I return back to San Francisco and set my notebook's time zone back to Pacific Time. In Lightroom, the Date Time Original of that photo is now 3pm. In Bridge, it still gives a Date Time Original of 6pm.
    Confusing? Yes, especially when traveling across lots of different time zones. In some cases, the Date Time Original will change not only the time, but the Date as well (if the change crosses midnight).
    Try it for yourself. Take a look at the Date Time Original of any given photo in Lightroom, change the Time Zone on your PC, and see the Time change for yourself.
    Since Bridge and Lightroom are both Adobe products, I have to wonder why they display EXIF times differently. Is this a bug? Or intentional?

    I have been als been plagued by LR displaying the capture time to be, say 3 AM (03:00), when I know I took the picture at 1 PM (13:00). I decided to try and see why this happens. With the help of Phil Harvey's exiftool, I can see that my Canon cameras embed the time into the EXIF data without any time zone information i.e.: Date/Time Taken = 2008:04:02 16:09:23.
    Here is what I found:
    If the image is now edited with Bridge, the information is changed to: Date/Time Taken = 2008:04:02 16:09:23-08:00 (time zone of the editing computer for the date the image was made. In this case the date was before daylight savings time started.)
    When edited with GeoSetter (good for adding GPS information) the information is changed to: Date/Time Taken = 2008:04:02 16:09:23+02:00 (time zone for Cairo where the picture was taken.)
    Lastly edited with LR, the information is changed to: Date/Time Taken = 2008:04:02 16:09:23-08:00
    When the above images are viewed in LR, using PDT, they display the time as 17:09:23 except for the image tagged with the Cairo time, which displays 07:09:23. If the computer's time zone is changed the displayed time changes accordingly.
    If the images are displayed with Photoshop CS3 all the times are correctly displayed as 16:09:23 as one would expect.
    It appears that the factoring in of the time zone into the displayed time was a conscious decision by the Adobe designers. A decision that several of us are not happy with.

  • Sorting photos by date/time taken, when date/time created is not an option?

    I'm so sorry if this has been answered elsewhere, but I can't find it on Google or in the forums...
    I need to sort wedding photos from multiple photographers by date taken so I can sort through the wedding as a full event. Sorting by the date/time the file was created will not suffice because I had to convert all photos from one of my photogs from NEF to DNG (D610 files not compatible with CS5), so the 'date created' for those DNG file is days later than all the other images. Thus, sorting by "date created' batches all the photos from one of my photogs together at the end.
    Is there any option in Bridge that will actually read the metadata and sort by the shoot time of the image?
    Thanks for any help!

      There has been a known bug in PSE9 although only affecting raw images and caused by the Camera Raw 6.4 update. The timestamp gets changed by one hour each time an image is modified. I don’t know if your issue is related but the work around is to revert to ACR 6.3
    http://kb2.adobe.com/cps/915/cpsid_91582.html
    The only other work around is to temporarily switch to folder location view, if your images were imported from a single folder. Click on the display button (near top right in Organizer) to change the browser view. If you click on the folder in the left hand pane the files will normally be in sequential file name order which usually mirrors the date/time taken. From the folder location it’s possible to create an instant album, which can then be used as the basis of a slideshow.

Maybe you are looking for