Easier Macro Creation

I'll say up front that this is going to sound like a rant.
I want SolidWorks to enable a simpler method for the creation ofMacros. I am not suggesting that they give up the API interface,just that they emulate macro creation for the rest of us whoneither have the time or the interest to learn programming. I'm notposting this in the API section because unless you are alreadycompetent in VB no one will answer your questions there (Iunderstand that posters there are busy and don't have time to teachAPI to total newbies to programming).

Let me give an example of what I mean:

I attempted to make a macro to rotate a component about apreselected edge and recorded all the picks as recommended. Thisincluded selecting "rotate about entity" from the drop box in theproperty manager. All the macro recorded was the selection of therotate command, not the mode of rotation. I searched the API helpand posted a question about it to the API group and have got noanswer from either ( again, I'm not blaming the API group for theirdisinterest) . I can only conclude that something this simple isnot possible in SW.

Now I have used many programs that allow you to record macros thatDO record menu picks, and also do not require subsequent editingvia programming to run. Photoshop is one where you record "Actions"that remember exactly which menu choices have been activated andthat are configurable on the fly to change values. Photoshop has aninterface built in to run your Actions on a batch basis.

Pro-E also records menu boxes you have picked with the option ofpausing for keyboard input before the macro continues, all withouthaving to edit code later to make it work (though you can read whatthe macro recorded and edit it).

These macro recording examples do not use VB to create them in (I'massuming it's all internal to the program). Again, I'm notdisputing the power of the API interface and don't want to see itgo away, I just want a more user accessible method of creatingmacros to make model workflow better. I'm sure I'm not alone here.
SolidworksGeneral