[squeak-dev] deselection broken in method list
eliot.miranda at gmail.com
Fri Jul 25 16:38:46 UTC 2014
I've had to inspect the damn thing and issue fileOutAllMessages manually
?!??! I'm not happy. We should not be in the business of breaking tools.
On Fri, Jul 25, 2014 at 9:37 AM, Eliot Miranda <eliot.miranda at gmail.com>
> Ugh, I changed the preference to not trace messages to get back a trusty
> MessageSet instead of a MessageTrace and now I can't even bring up a menu
> with nothing selected. I get prompted for a selector?!?!?! Who broke
> this? Will they *please* fix it asap.
> On Fri, Jul 25, 2014 at 9:27 AM, Nicolas Cellier <
> nicolas.cellier.aka.nice at gmail.com> wrote:
>> I hate the sticky-selection, and even more
>> select-something-when-I-press-yellow-button-before-popping-up-a-menu, not
>> my preferences.
>> 2014-07-25 18:21 GMT+02:00 Eliot Miranda <eliot.miranda at gmail.com>:
>> Hi All,
>>> I depend heavily on fileOutAll in method list browsers. For
>>> example, I'm trying to create versions of the VM's boolean cheat code for
>>> the Sista bytecode set and do this by filing out the code for the Newspeak
>>> set and editing it. I tried to do this using "self systemNavigation
>>> browseAllSelect: [:m| ('*ooleanCheat*V*' match: m selector) or: [m
>>> sendsSelector: #booleanCheatV4:]]" to get a method list browser. Then I
>>> was expecting to be able to use file out with nothing in the list selected.
>>> This files out all methods in the list but...
>>> Deselection is broken! I can't deselect the first item and hence can
>>> only file out a single definition . Will whoever changed this please
>>> restore it asap? (in trunk)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Squeak-dev