search

HappenApps / Quiver

Quiver documentation and issue tracker
2.26k stars 109 forks source link

Blank second pane when in three pane layout after 3.2.2 update #1228

Closed mobileben closed 5 years ago

mobileben commented 5 years ago

I updated to 3.2.2. I use 3 panes layout. Today is the first day I restarted Quiver after the update. Typically the second pane shows a list of all the notes in a notebook. However after starting. nothing showed up.

Let us say I am on notebook A. I found if I changed the Sort by Title then it would list the notes in notebook A. However if I changed notebook to B, then pane 2 would not change. It would still show the notes for notebook A until I changed the Sort By to Title. I also noticed that Sort By would be set to "(null)". I realized at the top it was marked as "Inbox". I clicked on the InBox in Library and a few other items and then it magically fixed itself.

Now when I click on the notebook, the notebook name will show up on the top of the 2nd pane. Note that (null) still shows up at times for some of the notebooks where it should say "Sort by". See screenshot as the example.

screen shot 2018-12-06 at 12 39 46 am
mobileben commented 5 years ago

Addition, something seems very broken. If you click on a notebook in the library that contains sub-notebooks and then click on the subnotebooks, the second pane will not update at times. It's spurious but happens at a high frequency.

Steps to create:

  1. Have notebook with nested notebooks.
  2. Be in 3 panes layout
  3. Click on parent notebook
  4. start to click down each successive notebook

Note that in second pane, the contents of the pane will not change and be stale. Eventually it will correct itself. Once it does, if you click on previous sub-notebooks that didn't have the notes show up in the 2nd pane, the notes will be listed

screen_shot_2018-12-06_at_12_50_24_am
ylian commented 5 years ago

This sounds really like a bug in 3.2. Please make sure you are running 3.2.2.

ylian commented 5 years ago

Okay, I realized that the fix I did in 3.2.1 didn't cover the initial run (first time after upgrade). All you need to do is to reopen the app. I will fix this edge case with the initial run as well.

mobileben commented 5 years ago

@ylian thanks for the reply. It is indeed 3.2.2. And you are correct. I restarted the app and the issue is gone.

ylian commented 5 years ago

Fixed in 3.2.3. Just released.