Download Picker
Edmond Peralto
My goal was to use elements (e.g. timelines, grids, calendars) to summarize project-level info in addition to the individual fields, and I wanted to use the projects record picker to filter both the elements and the individual project fields. The problem is that when you are using a record picker as your data source, you can only add elements for linked tables, and everything else has to be added as an individual field.
I am struggling to prevent my Apple pencil switching into the color picker mode with the magnifying glass as I'm drawing (happens on every 4th stroke or so, making the app unusable for me until I sort this out).
As a right handed user, even when I have cleared the screen so that only the context tool is showing the heel of my hand is pressed against that tool. So how do I disable the color picker feature, or can the context tool be moved to the top of the screen when its the only tool displayed so that it is out of the way of my hand
What you've described was an issue in an older Beta of Affinity Photo on the iPad but that was resolved and the only way i can get the colour picker now is by a long press, by that i mean, i have to stop moving the pencil and hold it still for a couple of seconds to get the colour picker.
I'm having the same issue with the color picker. When I'm drawing in small detailed areas, it's very hard not to activate the color picker with the pencil with the "long press", which is too short to me. I want to use the app mainly for sketching and painting. Sadly this issue is too big to me, I'm still be using procreate until this is fixed. Hoping to be able to disable the press-and-hold color picker activation within the brush tool.
Please make an option to turn off having the brush switch to the color picker. I am fine with the color picker being a tool that needs to be selected. Every other paint program has been that way for decades.
Too bad that after so much time this issue still is not fixed.
I'm mostly a "ink" illustrator, working with black lines all the time. I don't need color picker to show most of the time... and it happens ALL THE TIME, color switches from black to white (my bg) or wide grey spectrum when my palm lays on sketch underneath.
I bought an app that is not usable at this point. Frustrating to say the least.
Please let us disable the color picker gesture!
I have a new moodle site hosted in blue host (shared hosting). Initially I was able to add files (pictures, pdf) to the front page and to courses. Some weeks later though, I couldn't. When I click the 'Add an activity or resource' link and select a file to upload, for example, the file picker keeps loading infinitely as shown in the figure below.
I'm experiencing the same problem. File picker in the forums are not loading correctly into the page, but it is not consistent. The problem does not happen on some browsers, but is happening on other browsers and operating systems. It is also not consistent across the entire Moodle site. The file picker loads properly in assignment submission, but not on forum postings.
Did you find a solution to your issue? I have moved to ngixn and php7.0-fpm, and I am experiencing the same issue. When I try to upload a file with the file picker, it keeps spinning and it seems like it never upload the file; however, when I drag and drop the file, I do not have any issue.
I am having this issue too, but the suggestions in this (and many other file picker not working forums) didn't fix it. I recently updated the test instance of Moodle to 3.5.1 and this issue appeared (not on the clean install, so it is definitely something in our code). It is not from the additional css as I tried removing it and the problem persisted. Then I updated the code to 3.5.2 and the issue persists, that just confirms that it's being caused by our code, but it wasn't there in the previous versions (3.3.2).
I have unset the "Cache Javascript" parameter in "Site administration -> Appearance -> AJAX and Javascript" and the file picker gone back to work well. But, according the parameter description, this is not recommended for live environments.
If I click any parameter that should open the color picker, it just opens the drop down to select the individual RGB values, but not the actual color picker. Sometimes when I click it in random spots it will open, but for a fraction of a second and close again.
As I hold my right mouse button to make a selection, the color picker disappears instantly as soon as I release my right mouse button. This only happens when I try to make an actual selection whether it's color or alpha channel. When I click at the text shown below, strangely enough, it doesn't disappear.
Hello, Jira's built-in single select picker does not support both value and label properties so I am attempting to use ScriptRunner's Custom Picker ( -fields/built-in-script-fields/custom-picker) to create a very simple select that does this, however I am having some trouble because all examples use either an API or a DB connection to populate the list of options.
You can change the interpolated stings in renderItemViewHtml and pickerOption.html to combine the id/description differently (including hiding the id completely if that's your preference). Remember tho that the "id" value is what will be stored in the DB. But the description will be stored in the Index and fetched in real-time when you access the issue.
Hi @Tim22, welcome to the Asana Community Forum and thanks for taking the time to share your feedback with us! We have recently redesigned the date picker and you can now close the date picker using Enter, Esc or as you mentioned, clicking off the date picker to close it.
The isOpen property on ion-picker allows developers to control the presentation state of the Picker from their application state. This means when isOpen is set to true the Picker will be presented, and when isOpen is set to false the Picker will be dismissed.
isOpen uses a one-way data binding, meaning it will not automatically be set to false when the Picker is dismissed. Developers should listen for the ionPickerDidDismiss or didDismiss event and set isOpen to false. The reason for this is it prevents the internals of ion-picker from being tightly coupled with the state of the application. With a one way data binding, the Picker only needs to concern itself with the boolean value that the reactive variable provides. With a two way data binding, the Picker needs to concern itself with both the boolean value as well as the existence of the reactive variable itself. This can lead to non-deterministic behaviors and make applications harder to debug.
760c119bf3