forums > Products > Mori

"compacting search indexes" is evil? (or: slow)

Submitted by miragj on Sat, 2008-02-02 18:05. Tags ( )

Has anyone else noticed that the "compacting search indexes" bit when you close Mori takes longer than you would like? I have. My Mori file is less than 2mb, and I had been using a free version of Mori that I got from MacAppADay, or MacHeist, or one of those things that gave away software, and it was snappy. Closing Mori was near-instantaneous. Then, I upgraded to Leopard, and figured that I might as well upgrade Mori, as well, to avoid any Leopard incompatibilities (and because it was about time I paid for Mori, my favorite program I use)...

Now, imagine my disappointment, having just bought Mori 1.6.9, and discovering that it takes much longer to close than whatever OLD and FREE version I had been using. Sometimes it's almost as quick as it used to be, but more often than not, it's noticeably (and annoyingly!) slower. I use Mori specifically because it was so much snappier than any other similarly-featured program.

Please, someone, anyone, help me make it quicker!

Can the "compacting search indexes" thing be turned off? Or is this due to having made my Mori file in an older version of Mori? Or what? I really need to fix this. It's driving me insane.

--joe

PS- Hopefully this isn't a double post, but there's no forum search function that I could find, so...

‹ open files from sources in seperate windows without having them open in main window first "Updating search index" stalls ›
» login or register to post comments

Yes, this part of Mori got

Submitted by Tobias Weber on Mon, 2008-02-11 05:37.

Yes, this part of Mori got slower. And it seems even worse on Leopard than on Tiger.

But I'm sure this wasn't done to annoy users. Maybe our data is now safer from corruption, or Spotlight less likely to overlook something.

» login or register to post comments

Help menu and the Spinning Beach Ball

Submitted by rtebiz on Mon, 2008-02-18 12:48.

10.5.2 on a MacBook Pro (Intel)

Whenever I attempt to access the Help menu, I'm getting the Spinning Beach Ball of Death that last about 45 seconds. Mori is the only application where this happens and I think it happens every time I try.

Adventures in time: http://homepage.mac.com/bobembry/free/
Blog: http://homepage.mac.com/bobembry/iblog/

» login or register to post comments

help menu

Submitted by Rolf Schmolling on Tue, 2008-02-19 03:13.

Hi,
this has already been mentioned in another post to the forum. It seems that under Leopard, going to the help-menu accesses the whole of menu-items in the program whch includes the whole of the notebook-file-structure.

I donot know if there will be a way around this…

Greetings,

Rolf Schmolling M.A.

http://rolf_schmolling.macbay.de/

» login or register to post comments

But only in Mori do I get

Submitted by rtebiz on Thu, 2008-02-21 11:40.

But only in Mori do I get the spinning beach ball of death.

Thanks

Bob

Adventures in time: http://homepage.mac.com/bobembry/free/
Blog: http://homepage.mac.com/bobembry/iblog/

» login or register to post comments

rtebiz: re-read, slowly,

Submitted by Tobias Weber on Sun, 2008-02-24 17:50.

rtebiz: re-read, slowly, what Rolf wrote

Mori has an exceptionally large menu structure since it contains all folders in your file.

» login or register to post comments

I got it the first time.

Submitted by rtebiz on Wed, 2008-02-27 12:35.

I got it the first time. Don't care what the technical explanation (excuse) is. 85 % + of my day Mori is sitting in the background doing nothing. Surely there is a way to pre-build or get around this. I just timed it and it took 65 seconds for the Help menu to display. This is not Mac like performance.

Adventures in time: http://homepage.mac.com/bobembry/free/
Blog: http://homepage.mac.com/bobembry/iblog/

» login or register to post comments

You're Right, Performance is Sub-optimal

Submitted by Alfonso Guerra on Thu, 2008-02-28 07:38.

I took at look at Mori's behavior when the Help menu is clicked, and it's definitely off in Leopard. There's been a change in CoreData which is bringing in a lot of heartache. I was attempting to provide some solution in 1.6.10, but just kept fighting against the tools. With the release out, I'll be able to give better attention to learning their proper use.

Once I get to the root cause, I'll implement some changes to remedy your situation.

» login or register to post comments

Workaround for displaying the help menu

Submitted by M Hutton on Thu, 2008-02-28 18:45.

I have a really large notebook (thousands of entries) so it takes some minutes to show the Help menu.

One workaround for showing the help menu if you really need it, is to create a new empty notebook, then invoke the Help menu when that notebook is active.

Unfortunately this doesn't allow me to do 'Check and Repair Notebook' on my large notebook, unless I leave Mori and the spinning beachball in the foreground for a couple of minutes while waiting for the menu to drop down.

If this 'loading many menu items' issue isn't able to solved in Leopard, it would be useful to have a preference option to disable those dynamically generated menus (like 'copy to' and 'move to') which are causing the menu structure to be so big.

» login or register to post comments

Mori is Slower on Leopard, Yes

Submitted by Alfonso Guerra on Thu, 2008-02-28 13:04.

There's been a change to how CoreData handles objects which refer to one another, and for Mori notebooks there tends to be a few. The changes in the data loading means CoreData performs differently from before. Somewhat like the way changing the engine and suspension in a car gives it a different "feel" when driving, even though the interfaces for the driver (steering wheel, pedals, etc.) haven't changed.

As I continue rebuilding Mori's internals and get a better sense for what the interactions are "under the hood", you should see performance return to, then surpass, the previous levels.

Alfonso

» login or register to post comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.