Glitch with Button + opendialog
Don’t know if this has possibly been fixed in 5.0.4, but if you use a Button to bang an opendialog in 5.0.3, it stays lit (as though ‘mousedown’ were true) after the dialog closes.
----------begin_max5_patcher---------- 358.3ociSsraCBCD7r4q.4yzHLjGkdqeGQUUFvk3DXMBVToMJ+6EaCDSTPpW b1r6Ld1YWyUOBMU0KZo9u4ezmPt5QHlT5Djw+SnU79rRdqAFEDeqROSCrkPQ OZRqpEPtjWpJlJAcUpNrTfFdQiYsovepEVQoz.eZJGJn9eLB4KEfsxeM.XQa BGSKysBkd9E1jF0bL6jDJ9rQjg1Kjse2.kAhg5e1mnO0wyW+PeIgo1h4nIvq LZReuYvHTcgadd5if+4rIsCQE77A.asAvRy63x3nvYe1HZE.xQoBb85gsF6E eXxkO30zhLUopwhNbSBK9PztfUhtSa8wZR3ZJUJgKNhwzHF.jDxR16Fwb0ww VtynmuhV5kswCMdr4leMJd2hHWMzyaIHVv01ZiGFvNKaCSplyCeWXlJ57KeA zp5ZxlVly6M+6cPtnEkvrION+F1AyIYdtvTd54dkLuVIAbrIdnE8t48GqQo1 tC -----------end_max5_patcher-----------
Workaround: Throw a [del 1] between the button and the dialog, but this shouldn’t be necessary.
thanks for catching this and bringing it up. I’ll pass it along.
All the best,
On Aug 13, 2008, at 2:26 AM, mushoo wrote:
> Don’t know if this has possibly been fixed in 5.0.4, but if you use
> a Button to bang an opendialog in 5.0.3, it stays lit (as though
> ‘mousedown’ were true) after the dialog closes.
Not that this shouldn’t be addressed, but I think Max 4 did this, too.
I can see instances where I might like to have something similar to this functionality – say a ‘settings load’ button that stays lit if you’ve loaded a file from disk, or something, but I think there’s better ways to do that.
I donnon if Max4 did this or not, my max4 patches never had me opening dialogs. I rarely made patches designed for other people to use, but with the max5 presentation mode I’m leaning heavily towards a userbase of more than 1. :P
this should be fixed for the next incremental.