There now exists a special configured script called test_octave_interactive.sh which is run from plplot-test.sh whenever the --interactive_octave option is used with an interactive device option. The test_octave_xwin, test_octave_xcairo, test_octave_qtwidget, and test_octave_wxwidgets targets run this script for a range of "p" examples given in test_octave_interactive.sh(,in). Currently, the test_octave_qtwidget target works the best. However, even for that target the following "p" examples had to be excluded for the given reasons.
# 11 (many invalid limits);
# 12 (hangs);
# 14 (looks pretty to start but then segfaults);
# 17 (error: plrb: device is not xor capable, occurs for qtwidget);
# 18 (pthread_mutex_lock.c:285:)
# 19 (failed to exit properly for qtwidget, but wxwidgets was fine);
# 20 (failed to exit properly for qtwidget and wxwidgets)
Comments for devices other than qtwidget:
test_octave_xcairo panifully slow (issue reported previously for example 17 as bug 2960406 and therefore not anything to do with octave).
test_octave_xwin errors out (for any example) with
*** PLPLOT ERROR, IMMEDIATE EXIT ***
Can't open display
Program aborted
test_octave_wxwidgets seems to work fine on single examples, but segfaults whenever any second example is tested.
Some progress has been made towards fixing this.
Many of the problems were due to drivers not support plGetCursor. This has been fixed for xcairo and qtwidget. There are still a few issues with xor mode only being support with xwin / tk.
There is also an issue with the animation in example p14 with octave3.2.