On Thu, Feb 7, 2013 at 1:03 AM, Staffan Tylen <staffan.ty...@gmail.com>wrote:
> Here is another one for you, Mark. While verifying the changes you've made
> to fix the two issues I just happened to try ImageButton.rex, and that one
> causes the whole screen to go completely blank and it stays so for quite a
> long time. I don't know what makes the system come back again, I try
> various key combinations and then suddenly it's there. But the ooRexx
> environment terminates abnormally with the following information written to
> the Windows event log:
>
Hi Staffan,
I tested this with the 4.1.2 release 32-bit ooRexx and a 32-bit, 4.2.2.8952
version of ooDialog and there is no problem with the imageButton.rex
example.
Since you seem to be good at finding these, maybe I can teach you the
things you need to add to a bug report.
There is nothing more frustrating to a developer than to have someone say:
I ran your program and it crashed. And not supply any information that
might help the developer.
The information from the event log is of no help. The only reason it
helped yesterday was because I noticed that the version number for rexxpaws
was not correct for the 4.1.2 release of ooRexx, which caused me to think
maybe you were not running a 64-bit ooRexx. Which, if you had simply
reported that you were running a 32-bit ooRexx on a 64-bit system, I would
have been aware of from the start. ;-)
You at least need to give the frequency of the crash. Does this happen
every time you run it? Does it only happen once in awhile, say every 5 or
6 times you try the program? Did it happen once and no matter what you do
it didn't happen again?
You should at least try to run the program without using rexxpaws and see
if it still happens. Many problems in ooDialog are reported through syntax
conditions which are lost when you use rexxpaws. Plus, a lot of the
examples print to the screen. This output will sometimes be helpful in
knowing at exactly what point the problem happened.
Plus, in your case since you are building ooDialog yourself, you should at
least report if the same problem happens if you use the build from
SourceForge.
You should at least describe what you were doing when the problem happened.
Did you double click on the program icon in Windows Explorer and the
screen immediately went dark? Did you launch the program from the command
line using rexxhide imageButton.rex and the screen immediately went dark?
Did the program start okay and after you clicked on each button 10 times
the screen suddenly went dark? Was everything okay until you clicked the
Ok button to end the dialog and the screen went dark?
Normally you should always report the versions of the crashing program and
the OS details. But, since I now have that straightened out, ooRexx 4.1.2
32-bit release on Windows 7 64-bit using ooDialog 32-bit 4.2.2.8952, you
can probably skip it. Unless that changes. Since you are building
yourself, you should always report the svn revision, 8952 in this case.
Granted, if I can simply run the program and it crashes for me, then a
short I ran this program and it crashed is sufficient. But, a description
of how frequent the crash is and what steps you took to get to the crash
are always useful.
In this case, since I don't see any problems, I need the information above
to do anything further.
--
Mark Miesfeld
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users
