Google+ Checkvist community posts 2013-2018

Decisions decisions! I'm at a crossroads with Checkvist. One of the features that I am really missing is logic operators in filtering by tags. Without it pinpointing what I want to find across lists or even in one large list is really hard. This is the only thing that I miss from Todoist. Are there any plans to add NOT, OR, AND operators to filtering?

It would be really helpful if checkvist could respect unicode RTL while editing a task. Some of my tasks are in Hebrew, which is a right-to-left language. This can make things awkward when editing tasks or notes that have mixed RTL and LTR text or numbers and symbols. What I'd like is the following behavior: * When entering edit mode in either single line or multiline tasks, the text direction should change from ltr to rtl ("direction" property in CSS) and align to the right. Usually, I believe, the proper direction is detected based on either explicit direction symbols in unicode or the directionality of the first non-numeric non-symbolic letter character.) * When not in edit mode, the text should continue to align left on the outline by default, but it should still appear in the correct directionality. * There should be an option to change the direction of an outline manually. Some lists are purely in Hebrew. I did a small experiment and manually changed the direction o

I think localization needs some work. In particular, there are some start of week and timezone issues. I live in Israel, where the week starts on Sunday. However, I'm seeing all the calendars and checkboxes start with Monday. Also, in my profile, it incorrectly detects the timezone as being Athens instead of Jerusalem/Israel. In any case, I think it's a mistake to rely exclusively on detection. It makes sense to use it to set defaults, but both of these should be settings that the user can manually set. I travel often and use browsers in different countries. I expect to continue to see things "my way", and not whatever happens to be the "local way". It's just like language: if I travel to Russia, say, I wouldn't expect the interface to switch to Russian all of a sudden just because the timezone changed. That would be just a little bit confusing.

Are there any plans to add support for time? The issue is that most tasks don't need a specific time so the current mechanism is great, but there are tasks that have to occur at a specific time. This is especially important for daily repeating tasks, but there are other cases as well. For example, if I need to call someone in two days at 11:00, it would be great to get the reminder/notification at the right time.

Hi, is there any reason the hashtag symbol ("#") that prefixes tags was moved from CSS to a tag's actual HTML itself? The hashtag adds unnecessary noise to the tag list, making it more difficult to quickly scan a task's list of tags (since every tag starts with the same "#" character). It seems strange to force the hashtag display by default since tags have their own default styling (which is is effective at separating from a task's content).  Also, the hashtag is not displayed when editing a task's tags (e.g. via the "tt" shortcut), resulting in an inconsistent UX between viewing and editing tags. When the hashtag was added via CSS, I was able to hide it by using custom CSS rules.  However, now that this has been changed and the hashtag is now added directly to the CSS, users are stuck with this additional noise. It would be great if the hashtag was once again added via CSS, or that an option be added to hide it permanently. Thank you.

Dear community. I'm intrigued how CheckVist accomplished the following: ①　edit task opens a textarea　√ ②　pressing enter submits　√ ③　typing Japanese doesn't submit on the first enter key-stroke!!! I understand 1 and 2, but how do they accomplish 3? With a normal "text-input" I can accomplish this because enter is the default behaviour to submit the form, and the browser knows to not submit when typing Japanese. But CheckVist did it with a textarea! A textarea needs a custom way to submit on enter, like a keystroke handler (on keydown or something), but it clashes with typing Japanese........ Does anyone know how they did it?

I first tried out Checkvist for a while last year, but time pressures meant I had to shelve it. Anyway, I've just nearly completed another Pro trial period, and have to say I'm very pleased with it. The html5 mobile app is lacking in features right now (as I'm sure you guys are aware), but other than that, Checkvist is truly impressive in scope and execution. You should be proud of what you've achieved. I've just continued with a Pro subscription and expect to be making fairly substantial use of Checkvist over the next year. Cheers.

From the Checkvist reference doc (List Items->Details): "Non-Windows users can also view list item details temporarily by holding down Ctrl" I'm on a mac and this doesn't work for me. 'sd' does show the details as expected. For context, I was looking for a quicker way to grab a link to a list item. I don't think there's a keyboard shortcut for this? If not perhaps I'll put in a uservoice request.

API error - when will it be fixed? Very recently my curl script allowing me to create a Checkvist task from anywhere has broken As you can see from the screenshot I can get an auth token but the POST to create the Checkvist item (which was working last week) errors. Please can you fix it ?

If I email a task to a list with a due date attached, it gets dated a day early, eg. one with ^today gets a due date of yesterday, ^tomorrow becomes today, etc. I have my timezone correct in Checkvist's settings.

When opening the mobile app, I am more often than not presented with a 'Cannot update data, please sign out and sign in again' message. This seems to be mostly after a significant gap in use, and I'm not sure what the pattern is -- ie. whether it's time or number of edits done on other devices. In any case it diminishes the mobile experience. Is this to be expected? Is it just an artifact of the mobile app being immature?

How can I use CSS to remove this line? http://note.io/29h7URC