• 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

Multilevel Lists & Outlines

Hello all,

Is it just me, or is the Multilevel List button grayed out and unusable? Is this a feature not available in all situations, or not yet implemented, or something else entirely?

If multilevel lists are not available, how do others make outlines within Realmworks, if you do them at all?

Thanks
 
Grayed out for me too. I only create bullets and rarely numbered lists so it hasn't impacted me. What's interesting is that I haven't seen anyone else mention it on the forums.

Please submit it as a bug.
 
Huh. Confirmed. Like AEIOU, I've not used that tool, so never noticed the issue until now. I've used single-level ordered and unordered lists before, but really don't use the multi-level lists in the snippets. Actually, I more often "outline" using section headers.
 
This is not a bug we can fix. This is a limitation of the framework we use for Realm Works. It turns out that any use of multi-level lists within the framework will be completely borked when saved out as HTML. So we had to disable the feature when we switched to HTML last Fall. :(

If the framework gets fixed, we'll re-enable the feature. But it's out of our hands at the moment. Sorry!
 
Thanks for clearing that up. It's not a big deal. I tend to make outlines using the same method as MNBlockhead, but a few times I've found myself wanting to make multilevel lists and wondering at the inactive button.
 
No. Realm Works is still using the same version of the third-party libraries that rob mentioned above, so nothing has changed.
 
That's the same library blamed for preventing the migration to 64 bit. I wonder how many users would be willing to live with a change to the look of the UI for fixes to things like this as well as the underlying performance gains to be had from migrating to 64 bit?
 
Without being familiar enough with the DevExpress libraries, there should be 64bit version of those or a way to compile. If this is the library in question.
 
I thought so to when this came up years back but apparently not. Or at least LWD is choosing not to migrate for some reason, and I know migrating can be hard but at this part it is pretty much necessary.
 
Please change the model to something that suits you better LWD. I dont remember if i posted it already. Minor updates , compatibility and some goodies ==> free, major "expansions" that require considerable dev time paid upgrades.

So you have like 1 major per year and several minors. If someone skips one (or more) major releases he pays a bit more (or the other way around ppl who are regular buyers pay a little less).
 
Yeah, I've poked around on-and-off over the years trying to see the sorts of problems they might be facing going forward. It's hard when you don't actually own licenses for the products in question and can only go on what you can dig up from documentation and support forum posts. :(

FWIW, here's the third-party software you can see Realm Works is using based on the files installed with the application:

DevExpress Windows Forms controls (version 13.2)
Northwoods GoDiagram (Windows Forms diagramming)
Firebird Embedded Server
SharpZipLib

The files in the Master Database folder also seem to indicate that Realm Works uses a .NET variant of Apache Lucene for searching the database.

Please change the model to something that suits you better LWD.
Don't forget that online storage and access to Realm Works databases is a subscription product with the timer currently suspended. If they do ever get the Content Market officially released then the timers will be turned back on.
 
Don't forget that online storage and access to Realm Works databases is a subscription product with the timer currently suspended. If they do ever get the Content Market officially released then the timers will be turned back on.

Yeah I would provide a basic subscription for all buyers of a current major problably, they could still keep higher tiers for power users. When changing to paid updates I think the subscription model should not be the primary source of income. But I don't want to hijack this thread any longer :)
 
FWIW, here's the third-party software you can see Realm Works is using based on the files installed with the application:

DevExpress Windows Forms controls (version 13.2)
Northwoods GoDiagram (Windows Forms diagramming)
Firebird Embedded Server
SharpZipLib

The files in the Master Database folder also seem to indicate that Realm Works uses a .NET variant of Apache Lucene for searching the database.

Firebird definitely has a 64 bit variant.
I'm not familiar with SharpZip but there are Zip libraries that are 64 bit.
Lucerne is definitely 64 bit.


That leaves Northwoods and DevExpress.
 
They're all available in 64-bit or AnyCPU, at least in their latest versions. (Sorry for not including that info.)

That doesn't mean you can just change your compilation settings and have everything work, though. In my own applications I've run into issues trying to switch, and those applications weren't very dependent on the libraries they were using.
 
Last edited:
It's been a long time since I've done a migration but I've never done one, even one where that wasn't dependent on outside libraries, that there wasn't some problem.

This has been on of my primary complaints of this years longs debacles of stopping all development waiting to deploy the CM. Once they hit the wall and had to wait for Paizo they should have forked the codebase and started a migration to 64 bit.
 
Yep, but he LW world continues to revolve around CM oblivious of the meteor on the horizon......
Certainly a comparative analogy to the fate of the dinosaurs who thought they to were "cutting edge technology" hehehe
:D:p

Jokes aside, LWD needs Paizo far worse than the other way around. It would be to LWD benefit to follow a page out of DRivethruRPG script and at least generate some revenue via the community. DtRPG have big fish (Paizo, WOC, etc) and small fish (Kobold Press, Monte Cook, Green Ronin, etc) and just community users all in the same sand box supplying content for a multitude of genre and the laws of capitalism determine the value added via community purchase. I'm sure that was the LWD long term vision.... but to coin a casino analogy, "They don't make their money on the whales, they make it on the shrimp."

Finish the core elements that you advertised all the way back at the kickstarter when you said you were "nearly done" with those features. Individual PC / Player Reveal, Custom Calendars, etc.

From completion of that point, do as others have suggested and create more "custom tools" in house that could be added via a "pro version" 64bit here maybe? And / or allow creative users the ability to help you create other features and put them on the community "Content Market" since you obviously don't have the resources to do so yourself. I'd also caution that the nickel / dime approach is dangerous as well as it has killed many an effective idea (anyone remember the "brilliance" of WOC selling Dragon Magazine by the article?):eek:.

There are many talented people here anxious to add to what could still, in spite of everything, be a good tool. We are simply tired of having our collective hands tied behind our backs and being to told to wait and tread water when we all can see it drowning.:(
 
Back
Top