Yeah, I am using it in getParameters() because within the context of semantic search special page I cant use Parser::preprocessToDom() to parse some of my config parameters. In this case I use some fallback value for the special page. Otherwise, I think I had to use Parser::parse() and I am not fully aware of the consequences really. Wouldn't even know which parameters I should supply. So right now I am using isset( $wgParser->mOptions ) instead of mInline to check whether I am in an inline context or not.
I alreaedy noticed that mInline is working in handleParameters(), where I have to use it again to define for parameter 'name' that in non-inline context empty string '' is equally to null/unset while in inline context '' would be a valid value for the 'name'. (name='' or anything else for 'name' would create an non-visible output which would be veeery useless on the special page. Normally 'name' would not be set by the user if a "visible" output is required). Daniel Jeroen De Dauw wrote: > Hey, > > > It's in SMWParamFormat::doManipulation() where > > SMWQueryProcessor::getResultPrinter() is called, but with only one > > parameter, while the second parameter is defining the context e.g. > > whether the query is coming from an special page. Default is special > > page, so the context isn't set to inline for the result printing! > > This seems odd to me. Sure, the argument might not be passed here, but > then again, the query printer created here is only used to get the list > of parameters it supports and is then discarded. Later on a new query > printer is constructed for printing the actual output, which should get > the relevant argument as it did before. Are you using $mInline in > getParameters or any method called by it? If so, where and why? > > Cheers > > -- > Jeroen De Dauw > http://www.bn2vs.com > Don't panic. Don't be evil. > -- ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
