Search results for query: *

FYI, this is an actual bug. Extra QuickPads don't always get interpreted properly in Reflection.

Quickpads don't work consistently within Attachmate Reflections. There appears to be a bug in the code which makes them not work consistently. You're better off replacing them with Macros in my opinions, though this will require some learning on how to utilize the ribbon and work with ribbon...

What version of Reflection are you using? if it's Reflection 2014, go to File, Reflection Workspace Settings (at the bottom of the screen) and then in the dialog click on Set up API and Macro Security. Make sure it is set on Extra API otherwise it will get confused. HTH.

Unfortunately, what you gave me is using Reflection from several versions ago(2006). We upgraded to Reflections 2014, and I'm trying to document how to work with the very latest object model. I did finally get it to work, though. 'Declarations Private m_oApp As...

Check your legacy API preference. In Reflection 2014 you have to make sure that you are referencing the correct Legacy API in the Workspace or much confusion will proceed to occur.

I'm getting started with Reflection 2014 and the new object model and I'm running into an issue when trying to open a new terminal session. Right now I'm just playing around to get comfortable with the new model so I can start doing some actual work. 'I open the current Application...

Sorry..I haven't messed with the Quickpads at all, so I'm not sure what goes behind the button. My programming experience has always been at the interactivity with Office apps level. The Keyboard mapping is what I am wondering about, but I don't entirely know how to fix that.

there's no code involved that I can see. I don't have the Extra quickpad editor so I can't even see what's going on, beyond the quickpad button sending keystrokes like <Enter> and Attachmate not recognizing them as such.

for some reason the macros behind our existing quickpads will not work. They send the keystrokes <> but Attachmate does not interpret them as keystrokes it only interprets them as text. Anyone else seen this?

I'm still getting myself to the point where I'm completely confident in my OOP design skills so I'm looking for some feedback on a couple of different ideas and the best approach. I have an imaging app I'm working on for work with the following hierarchical structure: A batch of documents gets...