-
Notifications
You must be signed in to change notification settings - Fork 34
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
find solution for completion #1
Comments
@fuchsmich |
@fuchsmich what is the status now? I does not seem to work for me.. |
To me works (but not at the beginning of a line, have to modify the regex pattern for this to work). |
...of course there is still a lot to do. |
does not work here.... |
I'm using 5.8 in Archlinux and Windows. Ok, seems the 5.7 js-machine doesnt have this function. argh. |
...mabe we should support at least 5.6 which is the LTS version. |
still cannot test: |
please try again and post output with latest commit
…On Freitag, 14. April 2017 16:50:04 CEST oroulet wrote:
still cannot test:
file:///home/olivier/dev/qml-qtodotxt/qtodotxt/qml/QTodoTxt.qml:250:31:
Unable to assign [undefined] to QString
file:///home/olivier/dev/qml-qtodotxt/qtodotxt/qml/QTodoTxt.qml:250:31:
Unable to assign [undefined] to QString
file:///home/olivier/dev/qml-qtodotxt/qtodotxt/qml/CompletionPopup.qml:101:
TypeError: Property 'startsWith' of object (A) is not a function
file:///home/olivier/dev/qml-qtodotxt/qtodotxt/qml/CompletionPopup.qml:101:
TypeError: Property 'startsWith' of object (A) is not a function
file:///home/olivier/dev/qml-qtodotxt/qtodotxt/qml/CompletionPopup.qml:101:
TypeError: Property 'startsWith' of object (A) is not a function
file:///home/olivier/dev/qml-qtodotxt/qtodotxt/qml/CompletionPopup.qml:101:
TypeError: Property 'startsWith' of object (A) is not a function
file:///home/olivier/dev/qml-qtodotxt/qtodotxt/qml/CompletionPopup.qml:76:
TypeError: Cannot read property 'text' of null
file:///home/olivier/dev/qml-qtodotxt/qtodotxt/qml/CompletionPopup.qml:77:
TypeError: Cannot read property 'cursorPosition' of null
|
file:///home/olivier/dev/qml-qtodotxt/qtodotxt/qml/QTodoTxt.qml:250:31: Unable to assign [undefined] to QString |
must be some limitation of javascript engine in qt 5.7 |
how about current one?
…On Freitag, 14. April 2017 21:02:34 CEST oroulet wrote:
must be some limitation of javascript engine in qt 5.7
Can't we simply acces first character with str[0] in javascript?
|
What do you mean by current one? I pasted latest stack trace |
I replaced the "startsWith" method in last commit. |
works well now!! well done!. I will export projects, contexts and priorities as a property from mainController. |
new property completionStrings implemented and satt as model. This seems to work very well! |
Yes, it's nice. :) The visual stuff, connecting the proper events for opening
and closing and figuring out the keyboard handling took some time.
I will play around with the calendar widget but also 'd like to keep the
completion strings. I'm sure there are some, who prefer typing strings then
choosing the date from a widget.
…On Samstag, 15. April 2017 08:25:59 CEST oroulet wrote:
works well now!! well done!. I will export projects, contexts and priorities
as a property from mainController. But for dates I propose to replace the
old string based completion by a calendar widget popup. Do you give it a
try?
|
calendar widget looks very nice! good work as usual! With such a widget I do not think strings will be necessary, but we'll see... |
a small bug. If I choose 'due:' from autocompletion then the calendar pops up. But if I write 'due:' or get back to due: with backspace then not calendar pops up.. |
@fuchsmich and another bigger one: I select another task while the completion popup is visible then it stays visible and we get a coredump.... |
That's intended behaviour. The calendar opens only when you select "due:" from the Completionlist. |
It should not. Completion should appear on key press. Writing t: is faster without completion but you still want the calendar to pop up |
With some additional tweaking we could also use it in the search field. |
Yes
…On Wed, Apr 19, 2017, 16:22 Michael Fuchs ***@***.***> wrote:
With some additional tweaking we could also use it in the search field.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACcfzt16_b_DPTf-pvSfZHzyC7wAXh-Zks5rxhiygaJpZM4M4E6G>
.
|
not sure you need much tweaking... should work nicelly out of the box I
guess
On Wed, 19 Apr 2017 at 16:26 Olivier Roulet-Dubonnet <
olivier.roulet@gmail.com> wrote:
… Yes
On Wed, Apr 19, 2017, 16:22 Michael Fuchs ***@***.***>
wrote:
> With some additional tweaking we could also use it in the search field.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#1 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ACcfzt16_b_DPTf-pvSfZHzyC7wAXh-Zks5rxhiygaJpZM4M4E6G>
> .
>
|
something's different with the cursorposition between textarea
(taskedit) and textfield (searchbar).
Am 19.04.2017 um 16:37 schrieb oroulet:
… not sure you need much tweaking... should work nicelly out of the box I
guess
On Wed, 19 Apr 2017 at 16:26 Olivier Roulet-Dubonnet <
***@***.***> wrote:
> Yes
>
> On Wed, Apr 19, 2017, 16:22 Michael Fuchs ***@***.***>
> wrote:
>
>> With some additional tweaking we could also use it in the search field.
>>
>> —
>> You are receiving this because you authored the thread.
>> Reply to this email directly, view it on GitHub
>> <#1 (comment)>,
>> or mute the thread
>>
<https://github.com/notifications/unsubscribe-auth/ACcfzt16_b_DPTf-pvSfZHzyC7wAXh-Zks5rxhiygaJpZM4M4E6G>
>> .
>>
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACw_McQhTY92PjKxSN9YgXCP69i_6dnsks5rxhw4gaJpZM4M4E6G>.
|
Found out that TextField changes cursorPosition *after* textChanged is
emitted and TextArea *before*. o.O
Have no solution for this ad hoc...
Am 19.04.2017 um 16:37 schrieb oroulet:
… not sure you need much tweaking... should work nicelly out of the box I
guess
On Wed, 19 Apr 2017 at 16:26 Olivier Roulet-Dubonnet <
***@***.***> wrote:
> Yes
>
> On Wed, Apr 19, 2017, 16:22 Michael Fuchs ***@***.***>
> wrote:
>
>> With some additional tweaking we could also use it in the search field.
>>
>> —
>> You are receiving this because you authored the thread.
>> Reply to this email directly, view it on GitHub
>> <#1 (comment)>,
>> or mute the thread
>>
<https://github.com/notifications/unsubscribe-auth/ACcfzt16_b_DPTf-pvSfZHzyC7wAXh-Zks5rxhiygaJpZM4M4E6G>
>> .
>>
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACw_McQhTY92PjKxSN9YgXCP69i_6dnsks5rxhw4gaJpZM4M4E6G>.
|
This sounds like a big to report to qt |
No description provided.
The text was updated successfully, but these errors were encountered: