When developing Maui applications, I've frequently run into this
myself. I simply moving a Maui panel to another place on the screen,
when I drop it it disappears and I get a debugger.
That's when I realize, there was an inspector open beneath which
thought it wanted to accept that drop, but yet couldn't.
So, I totally agree with Karl. The situation above is the wrongest
thing the system can do -- it should either accept it successfully, or
not accept it at all.
On Wed, Feb 17, 2016 at 9:37 AM, karl ramberg <
[hidden email]> wrote:
> I would suggest we do as in Workspaces, that we can enable drop via a menu
> option.
>
> It seems the "feature" is more prone blow up because ofnaccidental drops
> than actual use.
>
> Best,
> Karl
>
> On Wed, Feb 17, 2016 at 2:47 PM, marcel.taeumel <
[hidden email]>
> wrote:
>>
>> Hi Karls,
>>
>> this seems to be a feature. You can set values for inst vars via d'n'd.
>> See
>> Inspector >> #dropOnFieldList:at:.
>>
>> However, do you have ideas to protect against inadvertent modifications?
>>
>> Best,
>> Marcel
>>
>>
>>
>> --
>> View this message in context:
>>
http://forum.world.st/BUG-List-in-Inspectors-accept-dropped-morphs-and-give-DNU-tp4878040p4878144.html>> Sent from the Squeak - Dev mailing list archive at Nabble.com.
>>
>
>
>
>
Locked
