Is it possible to use ant design's TimePicker to work using 99:59:59 instead of 23:59:59?
If so, how to do it?
Related
How can i solve this situation?
Assuming you are using Apache Isis 1.17.0, take a look at
wicket/wicket/resource/org.apache.isis.viewer.wicket.ui.pages.SidebarCssResourceReference/simple-sidebar-ver-1582544091730.css
and try to modify values for padding / margin. Eventually you need to override settings in application.css; sometimes you may need to use '!important'
If you are using Chrome, press <Ctrl>-<Shift>-C and select the date-time widget.
If you can provide sample code, I could take a closer look.
We are working on a React application (using Create React App without ejecting it) and we decided to use Ant as our base component library.
Now that we are near the end of the project, we discover that the application will be integrated into a corporate portal (WebSphere) as a "portlet", so we inherit all the CSS files from the main page.
Both frameworks seem to have their own reset styles, but they use different values.
So far, I have not been able to find a LESS variable in Ant that can be used for prefix all Ant's CSS rules.
Has anyone ever tried to make them live together?
We don't own the parent development, we can only make change on the React part, so only things related to Ant.
We finally go with a specific CSS patch file, and we add rules when needed.
Not really perfect, but none of the suggested path did the job we expected.
Here you can see some of the default antd variables.
One of them is #ant-prefix: ant;. I think you can change it and apply different styles.
That is a tough one, and at the end of development no less!
As #froston mentions, and which you seem to have tried the #ant-prefix: ant; in addition to this you will need to se prefixCls as a prop on every component instance you create, which will definitely be an exercise in self-flagellation.
Even if you set a global CONSTANT and import and use this with your components, you still have to thread it through to all the places, and will need to be appended with the component name.
By way of example, the defaultProps for an anchor is prefixCls: 'ant-anchor'.
Hope this helps and good luck!
I just update to version 15 of IntelliJ IDEA and everything is working well, but they've added a new feature at the top of the code windows for PHP and Sass indicating the namespace or class I'm in. I already know what namespace I'm in and what class/method/etc I'm working with so this just takes up room unnecessarily and when it changes I find it really distracting.
Anyone know what this is called so I can google how to remove it at least? I'd add the intellij-15 tag, but I'm short in rep in order to add new tags.
Go to Settings/Editor/General/Appearance and uncheck Show breadcrumbs.
I have TRAC 1.0.1 running.
For my tickets I would like to have a DueDate. Entering the DueDate should be done by using a DatePicker. Because it is convenient, and you can not enter wrong values.
I added following plugin to TRAC: http://trac-hacks.org/wiki/DateFieldPlugin
The description says, that it provides validation for custom fields and a DatePicker for Milestone and Ticket fields.
My trac.ini configuration file looks like this:
[ticket-custom]
duedate1 = text
duedate1.date = true
duedate1.date_empty = true
duedate1.label = Due Date
duedate1.order = 4
duedate1.value = DD-MM-YYYY
[datefield]
first_day = 1
format = dmy
separator = -
TRAC is now checking the input against the format. But what I really want is a DatePicker that pops up and lets me choose the date.
Any help is appreciated.
If the input is being validated but there is no datepicker it sounds like a client side JS / browser problem.
I just created a new Trac env, added the DateFieldPlugin, copied your [ticket-custom]
and [datefield] ini configuration and it seemed to work out of the box just fine. For example on /newticket I can see a datepicker for the Due Date field (using Firefox at least). Given that, all I can really do is give some more details which might help us debug your problem.
The datepicker is added via JavaScript. If you are running Trac 1.0 then you don't need to worry about jQuery or jQuery UI as Trac core now ships with these dependencies. You can see that by looking at the scripts tab in Firebug etc. when you are running tracd. Are you serving your own jQuery or jQuery UI scripts which might be conflicting? Are there any errors shown on the Firebug console tab?
The plugin serves extra JS files when you request certain pages in Trac, including /newticket and /ticket. You should also be able to see these scripts being served in Firebug etc. Is that true for you?
If you inspect the HTML in the ticket.html template displayed on /newticket you should also see something like this for the Due Date input
<input type="text" class="datepick hasDatepicker" value="MM-DD-YYYY" name="field_due_date1" id="field-due_date1">
Note the two datepick and hasDatePicker classes are what tell JS to to render a jQuery Datepicker dialog. Does your custom field have these classes? The plugin should be adding them for you (inside the post_process_request())
If all that is the same for you then maybe it is a browser problem?
While the plugin way was ok, when there was no other way, now it is only second best, because of all the limitations of storing date/time as formatted string instead of POSIX (micro)seconds, just like for other native Trac time fields.
There is a better way: Custom date/time field support has entered Trac core since 1.1.1 ("unstable" development branch moving towards next stable 1.2).
At least if you foresee heavy use and/or long term Trac deployment, you'll appreciate adding true timestamps to your db right from the start. It provides you with the best possible experience like date picker UI, full time zone and TracQuery support, even future time constraints ('nextday', 'nextweek', etc.) are possible right now.
A last note regarding Trac code stability: For what its worth I'm using true custom time fields support via patches in production since 2009 (Trac 0.13dev), runs smoothly in applications with 30.000+ tickets by now.
I want to update a live tile from a background task (and the lock screen badge, and show toast notifications). I've got code that works when the app is running, and it runs through to completion as a background task, but nothing happens to the live tile/toast/badge. I'm assuming that's because I need to use the overload of TileUpdateManager.CreateTileUpdaterForApplication() that takes a string, but I don't know where to find the string and/or what the format is.
Any ideas?
Package relative app identifier (PRAID)
Edit per comment: Have you tried the Application ID that you specify in the Manifest or the ID you use to create the Secondary Tile?