2.10 bugfixes

[goehle]

Changed parsePopUp so that it prints a list of options on a hardcopy. (Its not functional of course, but at least people can see what they would have been able to choose.)

[dpvc]

Note that this may change the formatting of the paragraphs. If the pop-up is part of a sentence, (like "the value A is (greater/less) than the value B", you will end up with

The value A is

   * greater
   * less

than the value B.

I'm not sure this is optimal. It might be better to use something like [A/B/C] if the options are short enough (and don't contain / or ]), and the itemized lists if they are long.

[goehle]

I changed it so that it prints inline as suggested when there are no more than 3 options with a total of less than 25 characters and no /,[ or].

Edit: Limiting the number of options and number of characters is wierd so I changed it to just limit the number of characters.

[dpvc]

The comment says 30 characters, but the count is 25. Is that to compensate for the brackets and slashes?

[goehle]

30 was too long in practice so I shortened it a bit. I'll recon the
comment too :)

On Tue, Dec 23, 2014 at 10:54 AM, Davide P. Cervone <
notifications@github.com> wrote:

In macros/parserPopUp.pl
#188 (diff):

@@ -119,7 +119,21 @@ sub MENU {
};
$menu .= "";
} elsif ($main::displayMode eq "TeX") {

• $menu = "\fbox{?}";

•  # if the total number of characters is not more than
  

•  # 30 and not containing / or ] then we print out
  

•  # the select as a string: [A/B/C]
  

•  if (length(join('',@$list)) < 25 &&
  

The comment says 30 characters, but the count is 25. Is that to compensate
for the brackets and slashes?

—
Reply to this email directly or view it on GitHub
https://github.com/openwebwork/pg/pull/188/files#r22220248.