Outliner with drag/drop reordering - part 2

cvp

@ihf said:

However, I came up with a different problem there. I was running v.13 and the script asks to update to v1.17. It then say V1.17 has been installed and I then close nd restrat the program but it does the same thing again. I can manually download v1.17 but I wonder why it is suddenly having this problem (or did I forget something?)

No idea comes to me, but now in my list. Late for me, thus .... later (not sure at all it could be tomorrow)

ihf

@cvp I downloaded manually and I'm back on v.1.17. I will test the date picker functionality now.

cvp

@ihf said:

However, I came up with a different problem there. I was running v.13 and the script asks to update to v1.17. It then say V1.17 has been installed and I then close nd restrat the program but it does the same thing again. I can manually download v1.17 but I wonder why it is suddenly having this problem (or did I forget something?)

I got the same problem on my iPhone and I retry and it was ok without manual install.
Not an explanation but if it happens again, retry to answer yes.

cvp

@ihf said:

However, I came up with a different problem there. I was running v.13 and the script asks to update to v1.17. It then say V1.17 has been installed and I then close nd restrat the program but it does the same thing again

Is it possible that outline.py was edited in Pythonista when you ran it?

cvp

@ihf V01.18 and outline.versions with

Version V01.18
    - correction of bug "on iPhone, modification of switch '1st level has outline'
      in menu of outLine formats does not work"

When I see that you find 3 bugs in a few minutes

this corrected one (at least hoped)
automatic updates download not working (not yet identified)
keyboard hiding last line on vertical iPhone (not yet identified)
I understand why apps have so frequent updates 😂 but I hate debugging

cvp

@ihf V01.19 and outline.versions with

Version V01.19
  - correction of bug "only on iPhone in portrait mode, editing the last line
    of a file bigger than a screen, the keyboard appears but hides this line"

smh

@cvp + @ihf What a great project! Trying to get V01.19 working on M1 MacBook Air, and below is the traceback, any ideas? Also, does using emoji break bullets/cause weird line break issues for other users? Keep up the great work!

"
Traceback (most recent call last):

File "/Users/<myusername>/Library/Group Containers/group.pythonista/Pythonista3/Documents/outline.py", line 97, in <module> load_ framework('EventKitUI')

File "/var/folders/tx/f122pq090xx2zc5ww_gtz0380000gn/X/3DCFE7F7-3144-5458-A0BE-545898853219/d/Wrapper/Pythonista3.app/Frameworks/Py3kit.framework/pylib/site-
packages/objc_util.py", line 934, in load_framework

return NSBundle.bundleWithPath_('/System/Library/Frameworks/%s.framework' % (name,)).load()
AttributeError: 'NoneType' object has no attribute 'load'

"

cvp

@smh said:

load_framework('EventKitUI')

I don't know why this line could give a problem on a Mac, sorry

You could try without this line, sometImes the framework is loaded by default

cvp

@smh said:

does using emoji break bullets/cause weird line break issues for other users?

I don'T understand, sorry

ihf

@cvp if I open one of my outlines that has about 14 lines in it and I position the cursor to the end of the first line the keyboard comes up but the outline is pushed up such that the insertion point is no longer visible. This is on an iPhone in portrait mode.

cvp

@ihf just tested and I see. What is weird is that if you scroll and retry to put your cursor at first line, the problem does not occur anymore. Annoying, I hate this kind of bugs

ihf

@cvp there is a problem when I type a long line (at least on the iPhone in portrait mode). When I get to the right side of the screen, the line is continued on the next line but the insertion point goes away (although the keyboard is still visible). In other words, I can’t type a line that has the automatic returns in it unless I position the insertion point after the word that has been moved to the next line.

cvp

@ihf said:

if I open one of my outlines that has about 14 lines in it and I position the cursor to the end of the first line the keyboard comes up but the outline is pushed up such that the insertion point is no longer visible. This is on an iPhone in portrait mode.

That happens only the first time when the keyboard is not yet appeared and my program does not know its height and the foreseen process to automatically scroll up to show a line under the keyboard is executed when it should not. Annoying, I'll check if I can correct it quickly.

cvp

@ihf V01.20 and outline.versions with

Version V01.20
  - correction of bug "before the keyboard has appeared a first time,
    the first edited outline is automatically scrolled up erroneously"

For your information, I get the keyboard height in keyboard_frame_did_change but this function is only called when the keyboard appears. I need to know this height because if you edit a row that would be hidden by the appearing keyboard, the row needs to be automatically scrolled up above the keyboard. But if you edit a row before the keyboard has appeared the first time, this height is not yet known. Thus I force the keyboard to appear and immediately be dismissed without we see it by creating, edit, end, delete a TextField during the general ui.View initialization. Magic, isn't it ?

ihf

@cvp Thanks for the quick fix to the scrolling problem. The lost insertion point on long lines that i mentioned above also occurs on the iPad in landscape mode.

cvp

@ihf said

there is a problem when I type a long line (at least on the iPhone in portrait mode). When I get to the right side of the screen, the line is continued on the next line but the insertion point goes away

I've seen that, and also on iPad as you said.

And you added

although the keyboard is still visible

Sure of that? For me, keyboard disappears

ihf

@cvp I just tested it again on the iPhone and confirmed that the keyboard remains visible although the insertion point disappears.

ihf

@cvp Probably an old Pythonista problem, but I just started a new outline entered three lines and then hit enter and Pythonista crashed.

cvp

@ihf said

Probably an old Pythonista problem, but I just started a new outline entered three lines and then hit enter and Pythonista crashed.

Unfortunately, this does not seem to be in my hands

But, anyway, try to check the reason in objc_exception.txt or faultlog folder

cvp

@ihf V01.21 and outline.versions with

Version V01.21
  - correction of bug "when typing a long line automatically splits the line,
    the keyboard sometimes disappears and cursor is no more visible"

As I can't reproduce your problem (in my case, keyboard disappears), perhaps this correction does not solve your bug (but only mine). Please, give me some feedback