Problem with virtual window manager

[CarlosM]

Congratulations for the latest generation of the ImgBurn program.

Now that it not only can burn ISO images, but also create them,

it is really becoming the small and easy CD writing utility

that I was searching for some time.

 

Unfortunately I can not really use it in the moment, because it

has a strange problem with my virtual windows manager.

I'm using the program "vern" (http://www.oneguycoding.com/vern/)

and the ImgBurn does not seem to like being handled by vern.

I can start it on one desktop, and when I switch to another one

and come back to the desktop where ImgBurn is running, the

ImgBurn window disappears and from there on it is impossible

to bring the window back. It really looks as if it flees away,

I see that vern hides it in some other desktop, but when I go to

that it has moved again to some of the currently invisible desktops.

 

Has the program some mechanism that it tries to move its window

to some suitable place which kicks in before or after a vern

desktop switch? Perhaps it doesn't notice that it has been moved

around by another program and thinks internally that the window

is somewhere else? I can provide some more technical

details I found out how the vern desktop switching works, but

that would be rather long so maybe is more suited for offline

exchange.

 

Regards, CarlosM

[LIGHTNING UK!]

I just downloaded + tried v3.60 and it all seemed ok to me. I'm running it on XP SP2.

 

When I switch to a different desktop the program + taskbar button vanishes (as one would expect).

 

When I switch back the button re-appears and the window (windows actually if you include the log one) are back on the screen.

[CarlosM]

I just downloaded + tried v3.60 and it all seemed ok to me. I'm running it on XP SP2.

 

When I switch to a different desktop the program + taskbar button vanishes (as one would expect).

 

When I switch back the button re-appears and the window (windows actually if you include the log one) are back on the screen.

 

That's a surprising result now, thanks for trying out that version.

 

And yes, like always, I should have mentioned versions and systems ;-)

I have the problem on Windows 2000 and XP. ImgBurn versions 1.3, 2.0, 2.1.

My vern version, however, is an old one, 1.5.

I never updated that to newer versions, because later ones all had various other

problems of their own.

I think this version is no longer available in public, at least not on the author's website.

I have still the original of this and a few more program generations here, so I think I'll

make some more tests with the various versions now and come back later when I find

something interesting (or when I find nothing new ;-)

 

CU, CarlosM

[CarlosM]

I have still the original of this and a few more program generations here, so I think I'll

make some more tests with the various versions now and come back later when I find

something interesting (or when I find nothing new ;-)

 

CU, CarlosM

 

Meanwhile I've tried out all vern versions that I had and the result is,

that the versions beyond 2.0 have no problems with ImgBurn.

So I finally made a update now to the latest vern version and

will see if this has fewer problems than the intermediate ones

which I had skipped.

 

Btw, if you have some spare time to try out the problem case

with the older vern versions, contrary to my first assumption

they are all still available in the vern website downlaod area.

 

CarlosM

[LIGHTNING UK!]

Borland applications (which is what ImgBurn is) are a bit weird in the way they work.

 

I guess the newer version of vern worked around this fact.

 

So basically, it was for them to fix and not something I could do even if I wanted to.

 

So long as it's ok with the current version (which it is) it's not really of any interest to me - sorry!

[CarlosM]

So long as it's ok with the current version (which it is) it's not really of any interest to me - sorry!

 

OK, I understand that ;-)

 

Unfortunately for me the vern saga has not yet ended. Now I have other programs

which have problems with the new vern (Firefox, Powerpost). So I still have the job

ahead to find a version which works equally well with my personal application mix.

 

But at least I think this week I finally can really start using the ImgBurn in production ;-)

 

CU, CarlosM

[linx05]

Why not ask the coder to fix the bugs?