Bo Peng wrote: > > I know, but it's easier to implement, and more consistent (users may > > wonder why there's the "no dialect" choice in some cases, in others not). > > And in listings, you can as well input "[default]Language" and "Language" > > OK. But you do not output and handle [default], do you?
No. But it's really easier to check for (dialectCO->currentItem() > 0) generally than to check if "No dialect" is there in every single case. Remember, "No dialect" is translatable, so we cannot just use dialectCO->currentText(). And I think it's debatable which solution is actually more intuitive. Jürgen
