Burnt Edge efx

pranderson:

BTW...I have LOTS and LOTS of macros installed in PP as well as CD, in fact, I've used several of them today. I have even created several macros myself. What's different about this one?

Hey I'm surprised too, it works great under XP but just tested it with Win7 (64) and I get the same errors as you.
Some things I've been able to find out: first you need mscomctl.ocx, which under XP is normally found in the system32 folder.
Under Win7(64) it apparently needs to be in the Windows\SysWOW64 folder (not here though), since it's a library for 32-bit controls.
See here

OK I got it working now .. copied mscomctl.ocx from my XP install to the SysWOW64 folder in Win7.
Registering the file (as described in the link I included in my last post) did not work, for some reason.
I then went to the VBA editor in PP (Alt-F11), and with the macro selected went to Tools > References, selected Microsoft Windows Common Controls 6.0, then clicked on Browse to change the path to the SysWOW64 folder.
Closed and re-started PP, and the macro now worked.

Success! And yes, I am using Windows 7 Professional 64-bit. The mscomctl.ocx file was already in my SysWOW64 folder, so I went through the command prompt steps to register the file.

Nice effect, BTW!

Patti

You probably don't want to debug an old macro, but I'm unable to run your latest version of burnededges.gms on 64-bit Win7 in PP X5 (SP1).  I've got mscomctl.ocx in SysWOW64, and registered, used your suggestion to set the reference in the VBA editor and immediately get the following error when running the macro:

 

Clicking OK gets the following error:

Any help will be appreciated.

drawken:

You probably don't want to debug an old macro

Not really, no :-) I could try, but have the feeling this error gets over my head.
Just some suggestions/questions:
Do other macros work? Can you get into the VBA editor? (If no, then it's probably not to do with mscomctl.ocx)
Does it makes a difference if you disable Win7's Aero, and/or run PP in XP compatibility mode?

I'm considering creating a version of the macro without the sliders, which would not need mscomctl.ocx at all, not sure though if that would help you?

Hi.

The code looks like it has nothing to do with the problem. It could be MS Forms and whether or not you have office installed. I've seen Office affect VBA before.

John

Here is a version that doesn't use the slider controls and hence doesn't need mscomctl.ocx.
If you still get error messages it's probably not due to this particular macro but a more general VB problem.

(Your link was to the jpg image, not the changed version BTW)

I doubt the problem is with mscomctl.ocx.  I have a couple of other apps that fail if mscomctl.ocx is missing and those apps are working OK.  I do have Office 2010 installed....

Yes, other macros work.  I can get into VBA without any problem, but running the burnededges macro immediately generates the above errors.  No way I'm going to disable Aero or run PP in XP compatibility mode for the sake of one macro.

Being a hobbyist programmer, I wouldn't mind bashing away at the macro in VSTA using C# if I could figure out what the macro is trying to do.

drawken:

(Your link was to the jpg image, not the changed version BTW)

NOT good at multitasking

burnededges_spin.gms works OK.

Thanks

drawken:

burnededges_spin.gms works OK.

Thanks

Great, I'll just consider this to be the final version then (and certainly the one I would advise for Win7).

 

I have D/L this GMS and I am unable to see it from corel. I put it in my draw gms folder and corel is not recognizing it. Can someone help on this please?

 

Thank you

You need to put it in the PhotoPaint GMS folder not the Draw GMS folder.
This will only work in PhotoPaint.

Steve
www.brutefish.com