You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This release fixes a couple of the known misbehaviors with v.20, the
"Mastermind Release":
* Nulti-word pet names are now fully supported and checked in their
entirety for uniqueness.
* The warning dialog that some pet names have errors, which is shows at
write-binds time, will only appear if binds are configured that
require pet names to exist and be unique. If by-name binds and
bodyguard mode bind keys are left blank, that dialog will be skipped.
TODO: still might update the red error display on pet names also only
to appear if unique names are required.
result=wx.MessageBox("One or more of your pet names has errors. You can continue to write these binds but they are likely not to work well in-game. Continue?", "Name Error", wx.YES_NO)
569
-
ifresult==wx.NO: returnFalse
560
+
ifself.Ctrls[f'PetSelect{i}'].GetLabel():
561
+
needUniqueNames=True
570
562
break
563
+
ifself.Ctrls['PetBodyguard'].GetLabel():
564
+
needUniqueNames=True
565
+
566
+
ifneedUniqueNames:
567
+
foriin (1,2,3,4,5,6):
568
+
ctrl=self.Ctrls[f'Pet{i}Name']
569
+
ifctrl.IsEnabled() andctrl.HasAnyError():
570
+
result=wx.MessageBox("One or more of your pet names has errors. You can continue to write these binds but they are likely not to work well in-game. Continue?", "Name Error", wx.YES_NO)
0 commit comments