Open eriktorbjorn opened 5 years ago
There is an object, DRIVE-CONTROLS, that looks like it's supposed to represent the controls in the Drive Bubble. They're not very useful:
DRIVE-CONTROLS
<OBJECT DRIVE-CONTROLS (IN DRIVE-BUBBLE) (DESC "control") (SYNONYM DIALS INDICATORS GAUGES BUTTON) (ACTION DRIVE-CONTROLS-F)> <ROUTINE DRIVE-CONTROLS-F () <COND (<EX-CHECK> <RTRUE>) (<VERB? ZAP> <RFALSE>) (T <TELL "You can't do anything with them." CR>)>>
But if they're supposed to be accessible, they should probably be in DRIVE-BUBBLE-ROOM, not DRIVE-BUBBLE.
DRIVE-BUBBLE-ROOM
DRIVE-BUBBLE
I guess it also needs NDESCBIT, and WHITE-KEY-FCN should handle so that it's either made visible/invisible or moved in and out of the room.
NDESCBIT
WHITE-KEY-FCN
If we want to enable this feature, that is.
There is an object,
DRIVE-CONTROLS
, that looks like it's supposed to represent the controls in the Drive Bubble. They're not very useful:But if they're supposed to be accessible, they should probably be in
DRIVE-BUBBLE-ROOM
, notDRIVE-BUBBLE
.I guess it also needs
NDESCBIT
, andWHITE-KEY-FCN
should handle so that it's either made visible/invisible or moved in and out of the room.If we want to enable this feature, that is.