star-options not determining cardtype
Support Ticket
Under "Tags" on http://grouppatternlanguage.org/wagn/testing_pattern click on "test tag 2" and you'll be offered to create a Basic card even though http://grouppatternlanguage.org/wagn/tag+*type+*options specifies it should be of type tag.
I think you want tag+*right, not tag+*type.
duh, thx, renamed to http://grouppatternlanguage.org/wagn/tag+*right+*options
However, http://grouppatternlanguage.org/wagn/testing_card%2Btag autofills off every card in the Wagn, not the nes in *options. (Cards that already exist restrict autofill properly, e.g. http://grouppatternlanguage.org/wagn/Rest_and_Action_in_Balance+tag )
--John Abbe.....Sat Dec 04 13:06:35 -0800 2010
tangentially, why does http://test.dwagn.org/wagn/beyond_type+*right+*options not actually restrict the autofill that comes up when you try to add pointer items to http://test.dwagn.org/wagn/foo+beyond_type ?
e.g. typing "m" should only show "might be a book" as it's in http://test.dwagn.org/wagn/beyond_type+*right+by_name but it shows many other cards as well
--John Abbe.....Sat Dec 04 13:22:32 -0800 2010
*options doesn't seem to work on new cards; there are a few support tickets about that but there should be a dev ticket. I think I see the problem in the code. easy to fix, though type_plus_right won't work on new cards without major effort. not clear on the beyond type thing. first guess is it has something to do with "or". could play around to see.
--Ethan McCutchen.....Sat Dec 04 21:41:56 -0800 2010
Either part of the "or" alone works, what else should I play with, or is that enough to file a ticket for make *options work with "or" ? (It would also be nice if cards added through the Pointer had their type set if one of the "or"s is a type. Ticket that as it's own thing? Or bundle with handle multiple types in plus-star-options?)
--John Abbe.....Sun Dec 05 03:30:14 -0800 2010
that's probably enough to make that ticket. my suspicion is that the problem is actually a general problem with "or" that somehow gets exposed in this options case. I'm not sure about that other "or" thing. warrants some discussion. maybe add to that "handle mult..." ticket for now to make sure it doesn't get lost?
--Ethan McCutchen.....Sun Dec 05 09:35:55 -0800 2010