The problem is fixed in MyInfo 7.0.9 (build 6843).

So, you prefer the old squares compared to the new arrows?

You need first to create a new form with the attributes that you want to use in the template as described here:
https://manual.myinfoapp.com/#_forms

Then you go to View > Templates, create a new note template and set the note Form to the newly created one.

Rod, I am unable to reproduce it. It is inprobable, but it could be some local conflict in the notebook. Can you send me the whole notebook or a portion of it at support@milenix.com?

Crystal401 wrote: ↑Tue Feb 09, 2021 6:43 pm Hi Petko,
I am using build 6799 and it has the same problem.

Please make sure that you have turned off the Empty Note formatting rule in Format > Conditional Formatting for each notebook.

Fixed in MyInfo 7.0.9 (build 6802).

Fixed in MyInfo 7.0.9 (build 6797).

The problem was caused by some huge notebook revisions that MyInfo was not able to store in the notebook. Now, it will behave accordingly, no longer producing an error.

Fixed in MyInfo 7.0.9 (build 6797).

I agree, Telesto. I will think about it.

I found that I couldn't search in Titles the same as in the Note Body so I spent hours copying the Title of every note into the top of each Note Body. Doing this I could use the asterisk wild card in front and behind the search term and it would find it. You have found an Easter egg indeed :) By de...

Actually, it is possible to sort by two columns in most cases. One sort column is set in the perspective and one can be added by clicking on a different column in the note list.

Bill, can you send me the section at support@milenix.com? I saw your bug reports, but I am not able to reproduce that.

You can also try recreating the perspective (not duplicating it) and see if it will sort properly.

Yes, I have found that cause of it. It will be fixed in the next update.

Yes, you can use the following shortcuts:

Maximize note list: Shift+Ctrl+T
Maximize note editor: Shift+Ctrl+E
Restore note list and editor: Shift+Ctrl+R

I've received the bug report. Hopefully this will be enough to fix it.