Closed GoogleCodeExporter closed 9 years ago
On our two other PCs (Win7), I will leave version 3.6 installed until this
issue is fixed.
NB. I missed downloading versions 3.7 and 3.8 from the IBT site, if they were
ever there. Ordinary Windows installation .EXE files (past & present) are not
listed in the deprecated downloads here in the code pages.
Original comment by DFH...@gmail.com
on 6 Feb 2014 at 9:35
xulsword 3.10+ no longer uses email to submit problem reports. Rather it
reports to a specific URL and so it no longer requires that an email client be
configured.
Various xulsword versions are now available as "MK" from IBT, see
http://ibt.org.ru/ftpmirror/pub/xulsword.
Not all versions are, or will be available. Some versions are development only
with no major public release for instance.
The error you reported above appears to be a UI locale related problem
(unfortunately the line number is cut off). Switching to English before
upgrading might possibly help. But I would like to know more about your
problem...
Original comment by gpl.prog...@gmail.com
on 11 Feb 2014 at 6:00
Good thinking about problem reporting. That's how many other programs behave.
Q. How do I obtain xulsword version 3.10 (.EXE) to try on my WinXP Notebook?
cf. Only the Firefox XPI is listed in
http://ibt.org.ru/ftpmirror/pub/xulsword/MK-3.10/
btw. I was already using English as the UI language.
What did you expect? I cannot read Russian.
NB. The error message was indeed longer than the width of the popup dialog.
How might I find out what was truncated?
Original comment by DFH...@gmail.com
on 11 Feb 2014 at 9:18
Could not de-truncate the error message, nor can the text within the dialog
panel be selected.
Original comment by DFH...@gmail.com
on 12 Feb 2014 at 5:53
Attached screenshot after dismissing the error dialog.
Windows XP Home Edition (SP3 fully patched) on Compaq Mini Netbook CQ10-101SA.
Original comment by DFH...@gmail.com
on 12 Feb 2014 at 8:03
Attachments:
Also observe the book selector seems to be too low down the LHS.
This was before installing any module.
Original comment by DFH...@gmail.com
on 12 Feb 2014 at 8:04
You wrote, "Maybe you could tell me what you were doing when the error window
popped up. Does it still do this? Or is everything working fine now? "
A. Occured after installation completes. Two email dialogs had to be dismissed
too!
B. Occurs again (always) just after opening the program.
Also observed in the taskbar a "temporarily hidden window".
cf. The taskbar item for the main window has no label.
Original comment by DFH...@gmail.com
on 12 Feb 2014 at 8:09
I can't think of much more to gather as evidence.
Original comment by DFH...@gmail.com
on 12 Feb 2014 at 8:10
I would like to test version 3.10 in which there's no attempt to report errors
by email.
If that does NOT generate the truncated error message, surely that would be a
vital clue?
Original comment by DFH...@gmail.com
on 12 Feb 2014 at 8:12
First the good news. I uninstalled MK, then installed version 3.1 (EXE) on my
Netbook. There was no error message dialog this time. That's a relief. Must be
a clue to what's going on.
Remember, my Netbook does not have an email client installed or configured. I
wanted to avoid inadvertently downloading from POP3 to my Netbook. On my other
PC, I use Thunderbird.
Now the neutral news: There was still in the Taskbar an item called
"xulsword-temporary-hidden-folder". Closing this did not cause any new issue.
Yet it's something I don't see in Windows 7.
Now the bad news: Clicking F2 or using the File Menu. No response. No attempt
to look for modules from the Internet. With no modules installed, changing the
number of Windows from 3 to 2 or 1 did not do anything. Always 3 windows.
Finally, the same poor layout of the passage selector. The top of the selector
was part way down the left hand side. I already sent you a screenshot from
version 3.9. Let me know if you need it from version 3.10
Original comment by DFH...@gmail.com
on 15 Feb 2014 at 3:42
Correction to typo: "then installed version 3.10"
Original comment by DFH...@gmail.com
on 15 Feb 2014 at 3:43
Further discussions continued by private email.
Original comment by DFH...@gmail.com
on 18 Feb 2014 at 10:16
Original issue reported on code.google.com by
DFH...@gmail.com
on 5 Feb 2014 at 10:07Attachments: