• 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

Couple of questions

S

ShadowWalker

Well-known member
How do you identify if a pick is added to a gizmo as apposed to the hero?
Important for knowing if you can access parent or not since it gives an error message when the pick is in the hero.

Also is there a way to have a dynamic table hide picks that were not directly added by that table?
 
1) container.ishero will = 0 for something inside a gizmo and 1 for something added to the hero.

2) Add an autotag to the table (which gets added to all picks added through that table), and then have the candidate expression hide everything without that tag.
 
Should have explained 2 better.
I have multiple tables displaying the same component/compset and I'd like for them to not display items added from the other tables.
 
Are the tables where these picks are being added on agent panels, and that's why a simple autotag isn't helping? In that case, put an agentautotag="" element on your table.

You'll also need to define that tag group as an identity tag on the component that's being used for the agents.

Then you'll need a field-based candidate expression, so that each agent pick can build its own candidate expression, that looks for its own identity tag of that tag group.
 
I have the tables on a form within a gizmo.
Drones in Interface Zero can have skills. Since they aren't all added to the gizmo like they are to the hero I thought the easiest way to do skills was to have a dynamic table for each level and have the user add skills as needed.

If there is a way to enmass all skills within the gizmo then I could do it the same way it will be done with the hero. With drag and drop. For now this works except for each table showing the skills added from all tables.

the Skill component has an identity already.
 
Are you shadowing these skills onto the hero, as well as displaying them within the drone's gizmo? Is that the issue that's requiring you to keep them from being displayed on the hero, too? If they're not shadowed/displaced, these skills would stay inside the container, and not be something that can be shown on the hero.

To figure that out, add a drone, add a few skills, and then in Develop...Data File Debugging, choose "Show selection list". Then, filter for one of the skills you're seeing duplicated on the hero, and look at the pick source and state for those skills - see where they're coming from.

Unfortunately, there's not a way to enmasse things to somewhere other than the hero container, although if your list of skills is relatively small, you could bootstrap them all, one-by-one from the <entity> that these drones use. It won't help if users add new skills - they can't alter the entity to add those skills to the list, but at least all the core skills would be there.
 
Last edited:
No they aren't showing up on the hero.
I have multiple tables on the same form all for skills. Similar to the way they are displayed in Fate. And when one table adds a skill the other tables display that skill as well in teal.
Not doing any shadowing.
 
Okay, so the autotags still seem like the best option - prevent things with autotags from other tables from being shown on any tables they don't belong on, or require the autotag from that table in order for something to be shown.
 
I'd use a single tag group, and use it only for this purpose. Then, you can write it in a simpler form:

Code: 
(SkillTable.1 | !SkillTable.?)

So that requires that it either have the tag for table 1, or not have any table's tag at all.

Or even simpler if there's no way to get a skill other than by adding it to one of these tables, meaning every skill that could be shown here will have exactly one of these autotags:

Code: 
SkillTable.1
 
This is why I shouldn't answer these questions quickly - list expression tests for that autotag, candidate expression does not, and should not inherit from the list expression. I'm sorry about that, I was just thinking candidate, because you can usually work with just that on most tables.
 
So I put in the <candidate> with nothing in <list>
(SkillPools.1 | !SkillPools.?) and the choose list coming up empty
I've also tried SkillPools.1 with the same results, and empty choose list
Should there be something in <list>?
 
I looked at the description of <list> and <candidate> on the wiki and they both talk about what gets listed in the choosetemplate for the user to pick from.
What I'm trying to do is to filter out items on the showtemplate.

28479742182_64ca9ece0f_m.jpg


from the above image. Notice was added to the table in the middle and what I want is for it to not show up in the two other tables.
 
Table 1
Code: 
      <candidate>
        <![CDATA[
          (SkillPools.1 | !SkillPools.?)
        ]]>
      </candidate>

Table 2
Code: 
      <candidate>
        <![CDATA[
          (SkillPools.2 | !SkillPools.?)
        ]]>
      </candidate>

Table 3
Code: 
      <candidate>
        <![CDATA[
          (SkillPools.3 | !SkillPools.?)
        ]]>
      </candidate>

There is nothing currently in <list>. I've tried putting things in there as well.
The skills component has both had and not had an indentity for SkillPools

At some point, once this is working, I need to add a !Skill.Hide into the mix as some skills are not supposed to be addable by the user.
 
Last edited:
Switch all of those to being list expressions, not candidate expressions.

Then, you'll add a new candidate expression, which is simply !Skill.Hide

P.S. There's a Hide group already defined in the skeleton files, which is intended for use in hiding things like this. I believe Hide.Skill is one of the tags that's already been defined in that group.
 
It is. It's where I got Hide.Skill from.
I added it to those skills I wanted hidden, but it was still showing them so I figured I needed to put something in to do so myself.
 
You must log in or register to reply here.
Back
Top