Ok, now tried even taking out referral to/use/implementation of the LBC (layout-by-code) module, in case that was causing hassles, since aside from compiled executables generated using either cx_Freeze, or pyInstaller, not wanting to cooperate, even the python code itself wouldn’t work running through python.exe interpreter on my test machines - both the VMWare instance of windows XP 32 bit, or my actual spare development laptop, what with both of them having all the same packages installed as am running on my primary, windows 7 64 bit development machine.
And it seemed that the moment was trying to invoke/call something related to it calling up an input dialog prompt was causing either compiled executable, or even python.exe interpreter to bomb out, with either mention of bad invocation of MSVCRT - included the redist folder under executable path, and double checked that version of .dll file matched what gets mentioned on wxPython wiki - or just telling me python.exe had stopped working, and, while it wasn’t an issue with just confirmation dialogue’s, it seemed to be any call to an instance of wx.TextEntryDialog.
And, have just included the following wrapper function in my own class code:
#—start code—
def DialogInput(self, title=“Dialog title”, label=“Field label:”, value=“Text value”):
sOut = “”
dlg = wx.TextEntryDialog(self, label, title, value, wx.OK|wx.CANCEL)
iResult = dlg.ShowModal()
if iResult == wx.ID_OK:
sOut = dlg.Value
dlg.Destroy()
return sOut
#end of DialogInput
#—end code
And, then call it in the following manner:
#—start code—
sNewName = self.DialogInput(title=“Add category”, label=“Enter new category name:”, value="")
#—end code—
But, same issue.
And, since I also replaced/implemented more detailed invocations of classes inheriting from wx.Dialog myself, for more detailed input, and since these work fine under either cx-Freeze, or py2exe compiled instances, but since it just doesn’t want to cooperate when calling the standard wx.TextInputDialog() function, I really don’t know what can be happening/causing so many hassles now…?
Another example is that something similar making use of wx.MessageBox and/or wx.SingleChoiceDialog works fine, so it literally seems to be when invoking something that includes a text box, but, my own implementation of class inheriting from wx.Dialog, with multiple text fields on it work fine.
Primarily, it comes down to that don’t want to have to carry on working around hassles such as replacing a standard call to a standard text input dialogue, by having to put together my own full on classes for something so simple, since it sort of points to some other underlying issue/error that am missing thus far, or something…?
TIA - and, mean that, since this is ‘building up’…LOL!
(hope haven’t missed/forgotten to mention something here)
Jacob Kruger
Blind Biker
Skype: BlindZA
“Roger Wilco wants to welcome you…to the space janitor’s closet…”