When I write a very simple GUI application with the UIPainter tool and
package it using Runtime Packager, I find that the packaged image still
allows me to use development hot keys like "doit" and "print it". This
is extremely dangerous in a packaged image and I'm surprised that the
Runtime Packager doesn't automatically turn these off.
These hot keys are created by the method UIFeelPolicy >>
keyboardDispatchTable where it correctly tests whether the feel policy
"supportsCodeEditing" before adding the development hotkeys in.
Unfortunately, supportsCodeEditing comes ultimately from the
ParagraphEditor and the ParagraphEditor initializes it to true:
initialize
super initialize.
self supportCodeEditingFeels: true.
charComposer := CharacterComposer new.
textHasChanged := false.
localMenuItems := #(#cut #paste #copySelection #formatSelection
#find #replace #again #undo #cancel #accept #alwaysAccept #hardcopy
#toggleWordWrap #doIt #printIt #inspectIt #debugIt #explain #fileItIn
#changeTextStyle #align)
There are no senders to set supportCodeEditingFeels to false and when
you package an image, you get the development hotkeys.
Am I doing something wrong? Why aren't development hot keys being
disabled automatically by the runtime packager? At the very least, the
ParagraphEditor >> initialize method should check whether it's in
runtime mode when it initializes the variable.
David Buck
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Locked
