I'm sorry for causing frustrations and will try to improve.

This is what happens: I double click on ImageButton.rex and the dialog start, but almost immediately after the screen goes completely blank/black. I can tell that something starts to loop, because the CPU fan starts almost immediately after. Previously I tried to exit the situation but pressing various keys, but I've now tried waiting, and after about 20 secs the picture returns again. The DOS window or whatever it's called nowadays shows the following:

Got ideal size: a Size (63, 1111928)
  width:  63
  height: 1111928

Got View Picutes button control image list information.
Returned: a Directory
  image list: an ImageList
  handle:     0x002E6058
  rect:       a Rect (1, 1, 1, 1)
  align:      Left
Image margins: 1, 1, 1, 1

Got Add Picutes button control image list information.
Returned: a Directory
  image list: an ImageList
  handle:     0x002E6058
  rect:       a Rect (10, 30, 10, 15)
  align:      Center
Image margins: 10, 30, 10, 15

The dialog window looks distorted, with a blank rectangle to the left that stretches downwards beyond the dialog window and overlays the Push Me button almost completely. The button appears briefly when hovering with the mouse over it. The program seems to be alive because the photo changes when hovering over it. If I press Push Me, the text in the text control changes but I can't see the left part which is constantly overlaid by the empty rectangle. If I press OK the program terminate normally. I was just going to write that it happens every time, because it did earlier, but now after closing it with the OK button the screen clearing doesn't happen any more. Also, the abnormal termination is gone. So I decided to restart the windows session and after that the screen goes blank, and when I try again it goes blank again :( I see no pattern in all this. But I've noticed that if I press keys on the keyboard in an attempt to clear the situation, then ooRexx abnormally terminates. I've also now tried to run it with rexxhide and the same thing happens except that the abnormal termination didn't happen after keying on the keyboard. Same thing with rexx but it took like 2 mins before the screen came back again, no abnormal termination though. I feel quite sure that I've tried this program in the past without any problems. Maybe Microsoft has introduced a bug?

I also tried to install the sourceforge version of ooDialog but it refuses to install, saying that I need to close the documentation and all oodialog applications, even after a fresh reboot! Don't know what's going on there.

ooDialog: ooDialog Version (an ooRexx Windows Extension)

ooSQLite: ooSQLite Version (32 bit) (Encryption enabled)
          Built Jan 31 2013 17:27:02
          Copyright (c) RexxLA 2012-2013.
          All Rights Reserved.

Rexx:     Open Object Rexx Version 4.1.2

SQLite:   SQLite Library Version 3.7.15
          2012-12-12 13:36:53

2012-12-12 13:36:53 cd0b37c52658bfdf992b1e3dc467bae1835a94ae
Encryption available: 1

I've also traced the program and the screen goes blank after executing the return from setPictureButtons. Actually when the screen is blank and I move and click the mouse randomly it has happened that the screen goes blank more than once in a single session. I get trace entries up to but not including

  isViewButton = (.DlgUtil~loWord(id) == self~constDir[IDC_PB_VIEW])

in onHover.

I hope this can be of some help.


On Thu, Feb 7, 2013 at 4:28 PM, Mark Miesfeld <miesfeld@gmail.com> wrote:
On Thu, Feb 7, 2013 at 1:03 AM, Staffan Tylen <staffan.tylen@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, 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, 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.
Oorexx-users mailing list