We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.
Sorry for re-asking this. I know I asked it before but can't find it. My CTRL+W stopped working. I tried the ALT+space bar, M, move cursor arrow tip, but that did not work. I remember seeing an option update the registry but cant' find it. What was the registry update process to resolve this issue (or is there a different, better way to resolve it)? Thanks.
I tried. Didn't work for me. I have a Windows keyboard key. When I use that option, it resizes my RH screen, but does not move/find/unhide the preview window. If I do the ALT + space bar, then M, then arrow, the arrow moves my RH screen. It's as if the preview window is not opening at all. If it matters, I do have two monitors hooked up, but I do not see anything moving on either monitor when following these step except the main RH project window. I know there was a registry key tip that worked for me the last time this happened, but I can't remember what/where it was.
My guess would be as you are suspecting. You aren't even getting the preview window to open. And if that's the case, even mucking about with the registry settings likely will fail miserably.
I'm personally wondering if somehow the keyboard shortcut got munged. What version of RoboHelp are you using?
I'm using RH 10. I installed a trial version of RH 2015 that has since expired. Not sure if that would be an issue. I'm not having any other issues with RH. Also, while I still definitely prefer using the RH CTRL+W preview window, the Multiscreen Preview window works from the View menu. I can't see as much at one time, but I can see how it will display and that's what I need.
Hokay, drawing from memory on this as I don't have RoboHelp 10 in front of me. (This computer only has 2015 Release)
I think if you right-click the toolbars you should end up with a dialog that has a few tabs that allow you to customize the icons, menus and Shortcuts. Hopefully the Shortcuts panel looks similar to the one in 2015. Here's what mine looks like:
Maybe find that and perform the reset, then see if things begin working?
Sooo, is that to say that this corrected your issue?