-
-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: allow timezone to be specified #67
Comments
@IkerrSC @jpara3 FYI |
What is intended to be is that the table that is shown in the timevis table gets the same time as the timeline shows. Not sure if being able to enable
will be enought |
To do that, you would use |
But where I have to do it? In timevis function?
And to add for example, UTC+1?
Thanks! |
As the documentation says, it's a parameter of timevis. |
I have tried with
And I have get: I have tried also
And it did not work
And also not working! |
Did you install the latest version from github in the past 30 minutes?
…---
Dean Attali
President & CEO
AttaliTech Ltd
http://AttaliTech.com <http://attalitech.com>
On Thu, 17 Jan 2019 at 00:35, jpara3 ***@***.***> wrote:
I have tried with
timevis(data,.....,timezone=1)
And I have get:
Unused argument timezone=1
I have tried also
timevis(data,.....,timezone=1)
And it did not work
Also I have tried adding
var options{
moment: function(date){
return vis.moment(date).utc();
}
}
And also not working!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#67 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA6IFJf41R7wfFSMPFxwXoS4s10W6Wxuks5vEBmhgaJpZM4aELOF>
.
|
I have tried with it, but not working
Here my app code:
|
I tried installing the package just now on 3 different computers and did not have an issue. Try restarting your R session and reinstalling the package. If you still see a problem with timevis and you think there's a bug, please submit a new issue separate from this |
What you're seeing is correct. For example, in the second example that you show, you're asking timevis to render as if it's in UTC+1, so in that timezone it's 00:00. If it's 00:00 in UTC+1, then in UTC it's 23:00. As I said a few times, timevis can only return information to shiny in UTC (that's what the Z means in the timestamp), so the return value of 23:00:00Z is correct because in UTC it is 23:00 when the timevis shows 00:00 If you still believe there is a bug, please submit a new issue for better organization |
OK Thanks for all! |
By default, the timeline displays times in local time, but it's possible to use
moment.js
to specify it to show in a different timezone; see #66The text was updated successfully, but these errors were encountered: