[17:42:23] <font color="#600060">Dominus:</font> Marzo, I should remind you of https://github.com/exult/exult/issues/159 :)<BR>
[17:42:39] <font color="#600060">Dominus:</font> I don't really dare removing the dragging check...<BR>
[18:22:23] <font color="#005000">Marzo:</font> Is there any object in the original games that calls UI_close_gumps when readying/unreadying it?<BR>
[18:22:55] <font color="#600060">Dominus:</font> I don't recall one at the moment<BR>
[18:32:45] <font color="#005000">Marzo:</font> Ah, there is the black sword in SI<BR>
[18:41:03] <font color="#005000">Marzo:</font> Huh<BR>
[18:41:24] <font color="#005000">Marzo:</font> The black sword is enough to prove that ready/unready events are delayed in SI<BR>
[18:42:40] <font color="#005000">Marzo:</font> Oh, I get it<BR>
[18:42:57] <font color="#005000">Marzo:</font> With that check, Exult kind of matches the behavior in SI when dragging the black sword<BR>
[18:43:28] <font color="#005000">Marzo:</font> With the check removed, as soon as you drag the black sword, gumps close immediately<BR>
[18:43:50] <font color="#005000">Marzo:</font>  Hm<BR>
[18:44:42] <font color="#005000">Marzo:</font> Delaying the ready/unready usecode to after gummps being closed leaves room for some exploits that happen in the original which I don't think work in Exult<BR>
[20:08:17] <font color="#600060">Dominus:</font> ugh, so I guess you want to do it properly. We *could* have added an extra exult intrinsic only for that, right? (UI_close_gumps_while_dragging)<BR>
[20:25:55] <font color="#005000">Marzo:</font> I added a long post in the issue explaining my findings, and proposing a possible solution<BR>
[20:31:41] <font color="#005000">Marzo:</font> It is funny that the first thing I tested was the one that would be broken by removing the check<BR>
[20:44:10] <font color="#600060">Dominus:</font> funny and good that you thought of that first<BR>
[20:44:20] <font color="#600060">Dominus:</font> so, it's complicated...<BR>
[20:45:12] <font color="#600060">Dominus:</font> I think, stuff currently works and without breaking the game somewhere, I think it would be best to add a parameter as you suggested<BR>
[20:45:41] <font color="#600060">Dominus:</font> and backward compatible, so that the parameter is not required?<BR>
[20:57:44] <font color="#005000">Marzo:</font> Yes, the parameter would be assumed to be false if it is not there<BR>
[21:07:30] <font color="#005000">Marzo:</font> On second thought, I think I will add another intrinsic with the new behavior. It will be easier on the documentation<BR>