• 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

Context Dependent Create Contained Topic

the_redbeard

Well-known member
When I use "Create Contained Topic" it would be helpful if RW was aware of what other topics are in the container.

For example, I have a container of game sessions for a group, and if I right-click and choose 'create contained topic', it would be helpful if RW noticed that every other topic in that container is a game session (or whatever) and have that be the default of the new topic instead of the last topic created.
 
When I use "Create Contained Topic" it would be helpful if RW was aware of what other topics are in the container.

For example, I have a container of game sessions for a group, and if I right-click and choose 'create contained topic', it would be helpful if RW noticed that every other topic in that container is a game session (or whatever) and have that be the default of the new topic instead of the last topic created.

+1 to this for sure since anything that saves clicks is good for my old fingers
 
-1 from me

This would be totally counter to how I, personally, do things.

In my realms, most of my containers do not contain a single type of topic. For example, I have Fort Whistler(Settlement) containing NPC List (Cast List containing NPCs), Walsh Estate (Adventure Area containing numerous Locations), Places in Whistler (Place List containing numerous Locations, Merchants (containing NPCs), A Geographical Region and Numerous Urban Regions)

So this would result in program confusion and extra steps from me when assigning contained topics
 
How about if you allowed a setting for the container that allowed you to specify a default topic type? If you included a 'no default' setting so it behaved normally, then it might be the best solution. Anyway, I wouldn't leave it up to whatever was already in the container, but make it a user selection probably by right clicking on the container and setting a preference.
 
How about if you allowed a setting for the container that allowed you to specify a default topic type? If you included a 'no default' setting so it behaved normally, then it might be the best solution. Anyway, I wouldn't leave it up to whatever was already in the container, but make it a user selection probably by right clicking on the container and setting a preference.

There isn't really a concept of a "container" type of topic. The "Cast List" topic is only used as a container because the name of the topic is "Cast List".

I much prefer the dialog to remember my last selected choice. However I would also like it to remember if I was adding it as a child to the current topic (which always gets reset to "no parent").
 
Back
Top