Welcome!
This is the community forum for my apps Pythonista and Editorial.
For individual support questions, you can also send an email. If you have a very short question or just want to say hello — I'm @olemoritz on Twitter.
Outliner with drag/drop reordering - part 2
-
Possibly try calling the dismiss with on_main_thread?
Are you getting a segfault with the dismiss, it something else?
-
Oh I see. Can you print the full traceback?
-
@JonB no error but nothing happens, perhaps I have to close the ui.View
-
@JonB if I close thé ui.View without dismissing, it is ok
-
@JonB said:
make sure you always change the drop-down to objc.
I hadn't imagined it would be any different, I'll try not to forget to check every time. again a huge thank you for your skills and your availability to help
-
@ihf I just begin to (try to) integrate the standard event editor. I have some questions:
- when we paste copied lines, if a line had already a due date, actually the program also sets the due date of the new line with the same date, I don't think that's normal. Do you want I don't set automatically this due date, so you could always set the due date manually
- you know that we have sometimes duplicate. As now, we know that the standard eventIdentifier is not unique but depends of the device, I will change that in the future but actually, I advice that you set/unset/update a due date (thus the event) always on the same device to avoid this possible generation of duplicates. Do you agree?
-
@cvp I agree that copied lines should not create a new due date for the same item. Yes, I agree that setting snd unsetting due dates from the same device is ok as a temporary measure but, of course, it’s not intuitive.
-
@ihf Sid:
setting and unsetting due dates from the same device is ok as a temporary measure
The problem that will follow is that, if I change the way to identify an event, by an unique value cross devices, What do do with old events? Support old way and new way or only new way?
And, it is probable that I'll begin with outlines events for Apple Watch, less important if bugs.
And you will need to be patient. I'm less motivated than at the begin of the development.
-
@cvp I dont think you should worry about “legacy” implementations (LOL).
I hope you are still enjoying development of what has become a very useful program. -
@ihf do you agree if for set/unset/update a due date event, I don't use anymore a separate datepicker nor an unset button but directly the standard event editor screen where you can
- delete the event (equivalent to unset)
- add a new or update and save an existing event
Or do you prefer I keep the datepicker, it's unset butTon and a new details buTton to get The standard event editor screen?
you are still enjoying development
New features, yes
-
@cvp my personal preference would be the latter, keep the current ability to set and unset but allow the addition of details through the event editor panel.
-
-
@ihf sad:
I dont think you should worry about “legacy” implementations
When I'll modify the way I check an unique cross devices identifier, in a not immediate future, that will say you would no more be able to update events of old way. Or I don't understand your sentence.
-
@ihf V01.17 and outline.versions with
Version V01.17 - a new 'details' button in the datepicker (set due date) view, will allow to add/update/delete an event via the standard event editor, so all fields like second alarm and repetition would be available - unset a due date will delete the associated event with all its future occurnces - when a row is pasted, if it had a due date (and event), the new row will not have its due date set, thus no new event will be added
Please, do some tests with
- set datepicker then tap outside
- tap unset
- tap details
- with new event: add, cancel
- with existing event: save, cancel, delete
And give me some feedback. If no problem, I'll begin to study protection via a cross devices id.
-
@cvp I know you’re not thrilled to hear about bugs but just now I opened an outline and double clicked on a word in the last item and the keyboard appeared (portrait mode on iPhone) and covered the line that I was editing. This may be an old problem but then I realized that the outline had three different lines at level 1.0 and two of those had child nodes at 1.1. I don’t know how the outline got this way but other than deleting and starting over I’m not sure how I would fix it either.
-
@ihf said:
I know you’re not thrilled to hear about bugs but just now I opened an outline and double clicked on a word in the last item and the keyboard appeared (portrait mode on iPhone) and covered the line that I was editing. This may be an old problem but then I realized that the outline had three different lines at level 1.0 and two of those had child nodes at 1.1. I don’t know how the outline got this way but other than deleting and starting over I’m not sure how I would fix it either.
Oups. Not easy for me to understand the problem, thus to solve it. Sorry
-
@cvp I can't send the actual outline but There a re multiple lines that say 1.0 (4 of them at different places in the outline. It may be related to using the 1st level is not part of the outline?
-
@ihf said:
I can't send the actual outline but There a re multiple lines that say 1.0 (4 of them at different places in the outline. It may be related to using the 1st level is not part of the outline?
I think it is normal.
The 1st level does not have outline, Thus 2nd level begins with numbers of 1st level.
Aaa
1.0
2.0
Bbb
1.0
2.0 -
@cvp If I turn on "1st level has outline" it turns itself back off after I leave the menu.
-
@ihf see my previous edited post