• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

HELP: How to open realm but NOT open previously opned tabs?

Is there a way to tell RealmWorks NOT to open a realm with the previously opened tabs open?

One of my tabs is causing a crash (I sent a report) every time and I can't get to ANY content in that realm now.
 
Tried deleting local preferences.... RW is still crashing and RW is still trying to open the same tabs.

I can open other realms (but not the one I really need).
 
Apparently I wasn't deleting the RIGHT local preferences... for others having this issue... it was not the delete local prefs on the Tools menu of the launcher... instead it was an item under a little pop up menu next to the realm on the realms list.

Now I can at least open my realm, but a simple search caused a crash (sent a bug report).
 
You can issue a bug report.

Another thing to try is to open the realm and press the button to perform a re-index. This sometimes solves this sort of problem.
 
Maybe RW should keep track and pop up a requester every n'th time a realm is opened

"It has now been n times since you last re-indexed the database. It is recommended you do this every now and then. Do you want to: Do it now, postpone it to later, never bother me with this again?"

I myself keep forgetting this little trick.
 
Could be done - I was under the impression that it could take quite some time for guys with a very huge realm that had lots of changes to it over time.

If this is the case (it taking a long time) I would hate for it to start automatically (like Win10 updates - "you are in a hurry? No worries, this will just take a couple of minutes or five and we already started"),
 
You shouldn't have to do it at all.

If RW is messing the index files up in unknown ways we should be reporting bugs and keeping the database/index/prefs/etc. files around until LWD knows whether or not they need them.

If they get messed up in known ways that aren't fixable (perhaps due to third-party software bugs) RW should fix or wipe and rebuild the affected files for you rather than letting you continue and cause problems.

Reindexing, deleting prefs, and such should be viewed as a workaround for a symptom, not a cure for the underlying problem or a regular maintenance feature.
 
Last edited:
You shouldn't have to do it at all.

Reindexing, ... , not a cure for the underlying problem or a regular maintenance feature.

(Heavily edited quote...)
I am referring only to the re-indexing bit.
Re-indexing is a standard procedure in any database form large to small...
It's a standard operation for every DBA.

Now how to solve it in a customer facing program is a different issue.
Do they go down the root of user unaware operations? (and get complains for "why is it starting/closing so slow every 10 time...")
A nagging pop up every so often? ("why are they bothering me 10 minutes before game start?")

Also taking into account that the length of the operation is unknown.
 
Certainly not every 10 or even every 100 edits.

But Re indexing every, say, 6 months or 10,000 edits should be automatic. As Avi said it is a standard operation for a DBA maintaining a db. But then there is the time factor so maybe the annoying popup is the way to go, "Your realm is in need maintenance! press this button!"
 
Before I go too far into the weeds*, are we talking about the indexes internal to a database or what the Rebuild Index button does?

The Rebuild Index button in the Realm Works UI, from what I understand, only deletes the index files used to search the text in your Realm Works database. They're stored separately from your master.realm file, in the individual realm's UUID folder in your master database folder. (The third-party search engine in use is Apache Lucerne.Net, if you care.) It doesn't do anything to the internal database indexes.


* "Too Late!" ;)
 
Last edited:
I wasn't aware there was a difference, if there is one. IME the rebuild index button fixes a lot of the problems I expect to see fixed by rebuild corrupted db indexes.
 
Hmm...well, I can't tell from the comparisons I did yesterday and don't feel like going through the rigamarole to make single realm master.realm files to make the comparisons go faster, so who knows? I'm probably wrong again. :(

If you'd like to laugh along a bit with Mr. Thinks-He-Knows-It-All, I got Realm Works to crash a bunch of times yesterday while I was making copies and doing comparisons before and after doing Rebuild Index. It was intermittent so I was getting frustrated and a bit worried that I'd managed to screw up the database itself...until I finally realized that I was keeping the index folders locked by having them selected in Explorer. ::sigh::
 
Hmm...well, I can't tell from the comparisons I did yesterday and don't feel like going through the rigamarole to make single realm master.realm files to make the comparisons go faster, so who knows? I'm probably wrong again. :(

If you'd like to laugh along a bit with Mr. Thinks-He-Knows-It-All, I got Realm Works to crash a bunch of times yesterday while I was making copies and doing comparisons before and after doing Rebuild Index. It was intermittent so I was getting frustrated and a bit worried that I'd managed to screw up the database itself...until I finally realized that I was keeping the index folders locked by having them selected in Explorer. ::sigh::

Don't worry about it. I've found any number of ways to crash RW by doing things while testing stuff that would never come up during normal use.
 
Back
Top