<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Apr 4, 2012, at 9:23 AM, ale rimoldi wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">but before a dialog can be programmed, we have to know what the "bad"<br>action is...</span></blockquote></div><br><div><br></div><div>for lack of programmers' language, I'd say the bad behavior in this case is Scribus getting "locked" into a repetition of the blinking arrow combined with being unresponsive.</div><div><br></div><div>You are completely correct that, by continuing to press on the space bar, I am giving Scribus the same input which produces the arrow blink.</div><div><br></div><div>However, for the *user* to gain productive communication from this, a dialogue box would go much further than the punishment as another said, of a program sitting there, blinking and being un-responsive.</div><div><br></div><div>Now that we've had this conversation, I know the error of my ways. New users are likely to be as confused as I was.</div><div><br></div><div>I have nothing more to add to the subject. thank you for reading!</div><div><br></div><div>dcat</div></body></html>