suzanne.soy/racket
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

set the locked state flags during the initialization of a text% object (this bug found by random test case generation)

Browse Source 
svn: r18475
This commit is contained in:
Robby Findler 2010-03-05 19:43:50 +00:00
parent 1cbb303594
commit c2d9b0dc3e
1 changed files with 12 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
collects/mred/private/wxme/text.ss
View File

@ -111,14 +111,10 @@
on-edit-sequence
after-edit-sequence
on-display-size)
(define is-locked-for-read? #f)
(define is-locked-for-flow? #f)
(define is-locked-for-write? #f)
(define read-locked? #f)
(define flow-locked? #f)
(define write-locked? #f)
(define read-locked? #t)
(define flow-locked? #t)
(define write-locked? #t)
(define hilite-on? #t)
@ -333,7 +329,15 @@
(define tabs (list->vector tab-stops))
(make-only-snip)
(set! read-locked? #f)
(set! flow-locked? #f)
(set! write-locked? #f)
;;; from here on, it is only method definitions,
;;; so we can unlock the editor now. If code with
;;; effects is added below, be sure to move the
;;; unlocking.
(def/override (~)
(set! word-break-map standard-wordbreak)
(let loop ([snip snips])