'Alt Gr' (or Ctrl+Alt) in CC 2014 extension?
Hi,
I'm currently in the process of creating my first extension for Premiere Pro CC 2014 using HTL5/JavaScript/ExtendScript, and I've noticed a rather peculiar behavior (at least from my point of view).
I'm using a German keyboard and I'm unable to enter any key in combination with 'Alt Gr'. For instance, I need the users to enter '\' ('Alt Gr' + ß) or '@' ('Alt Gr' + Q) in grid cells or textinputs, and nothing is happening. On the other hand, in the search input field in the 'Metadata' window, when entering a new name for a bin for instance all these key combination are working as expected.
I've already removed any keyboard shortcuts that may interfere with these combinations, but with no result. I've also downloaded and installed other extensions and add-ons, which have input fields, but the keys won't work there either.
So my question is: Is there anything I can do (maybe in the manifest.xml of the extension, or some setting in Premiere itself) to allow these 'Alt Gr' key combinations within my Premiere extension?
Thanks in advance!
Ask in the relevant scripting forums.
Mylenium
Similar Messages
-
[SOLVED] Ctrl+Alt+S and Ctrl+Alt+O Blocked by ?
Hi!
On a new arch+gnome system, I cannot bind any command to the Ctrl+Alt+O and Ctrl+Alt+S shortcuts in pycharm.
Going through all the shortcuts in gnomes' Keyboard > Shortcuts and via dconf-editor, I cannot find any program that binds to these shortcuts.
Any advice?
Last edited by nonZero (2015-05-19 07:10:58)When using xbindkeys -k , I get this for ctrl+alt+s or ctrl+alt+o:
"(Scheme function)"
m:0xc + c:64
Control+Alt + Alt_L
Which is very strange, because it does work correctly for other shortcuts, for example, ctrl+alt+a:
"(Scheme function)"
m:0xc + c:38
Control+Alt + a -
Can't switch VT's with Ctrl+Alt+Fx or Ctrl+Alt+backspace terminate
Ctrl+Alt+F2 doesn't seem to register. It's been a long term issue I have had for years. I've tried all the various fixes.
I can manually change to virtual terminals without issues using:
sudo chvt 2
Once I'm in a VT I can use Alt+Fx to change between them, until I go back into Xorg. So it's unlikely to be a graphics driver problem, most other people with similar issues complain of getting a blank screen.
Although without sudo I get
# chvt 2
Couldn't get a file descriptor referring to the console.
I have the following in /etc/X11/xorg.conf.d/15-forcevt.conf
Section "ServerFlags"
Option "HandleSpecialKeys" "always"
Option "DontVTSwitch" "false"
Option "DontZap" "false"
EndSection
Section "InputClass"
Identifier "Keyboard Defaults"
MatchIsKeyboard "yes"
Option "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection
A also enabled the terminate option in gnome-tweak-tool.
xmodmap -pke has the following:
keycode 67 = F1 F1 F1 F1 F1 F1 XF86Switch_VT_1
keycode 68 = F2 F2 F2 F2 F2 F2 XF86Switch_VT_2
Nothing is printed in Xorg logs when I try pushing the keys.
I'm using SLIM (although I tried manually via startx), AwesomeWM (also tried fluxbox with a blank conf), nvidia (proprietary), UEFI.
[ 2490.220]
X.Org X Server 1.17.1
Release Date: 2015-02-10
[ 2490.225] X Protocol Version 11, Revision 0
[ 2490.227] Build Operating System: Linux 3.18.6-1-ARCH x86_64
[ 2490.229] Current Operating System: Linux ender 3.19.2-1-ARCH #1 SMP PREEMPT Wed Mar 18 16:21:02 CET 2015 x86_64
[ 2490.229] Kernel command line: BOOT_IMAGE=/@/boot/vmlinuz-linux root=UUID=ff84efeb-e43f-47fe-a14d-07894feb0013 rw rootflags=subvol=@ quiet
[ 2490.233] Build Date: 14 March 2015 06:45:50PM
[ 2490.234]
[ 2490.236] Current version of pixman: 0.32.6
[ 2490.240] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 2490.240] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 2490.247] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Apr 1 10:44:03 2015
[ 2490.249] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 2490.250] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 2490.250] (==) ServerLayout "Layout0"
[ 2490.250] (**) |-->Screen "Screen0" (0)
[ 2490.250] (**) | |-->Monitor "Monitor0"
[ 2490.251] (**) | |-->Device "Device0"
[ 2490.251] (**) |-->Input Device "Keyboard0"
[ 2490.251] (**) |-->Input Device "Mouse0"
[ 2490.251] (**) Option "DontVTSwitch" "false"
[ 2490.251] (**) Option "DontZap" "false"
[ 2490.251] (**) Option "Xinerama" "0"
[ 2490.251] (==) Automatically adding devices
[ 2490.251] (==) Automatically enabling devices
[ 2490.251] (==) Automatically adding GPU devices
[ 2490.251] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 2490.251] Entry deleted from font path.
[ 2490.251] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 2490.251] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 2490.251] Entry deleted from font path.
[ 2490.251] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 2490.251] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/
[ 2490.251] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 2490.251] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 2490.251] (WW) Disabling Keyboard0
[ 2490.251] (WW) Disabling Mouse0
[ 2490.251] (II) Loader magic: 0x815d80
[ 2490.251] (II) Module ABI versions:
[ 2490.251] X.Org ANSI C Emulation: 0.4
[ 2490.251] X.Org Video Driver: 19.0
[ 2490.251] X.Org XInput driver : 21.0
[ 2490.251] X.Org Server Extension : 9.0
[ 2490.254] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c1
[ 2490.254] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 2490.254] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8 paused 0
[ 2490.258] (--) PCI:*(0:1:0:0) 10de:1180:10de:0969 rev 161, Mem @ 0xfa000000/16777216, 0xf0000000/134217728, 0xf8000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 2490.258] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 2490.258] (II) LoadModule: "glx"
[ 2490.258] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 2490.268] (II) Module glx: vendor="NVIDIA Corporation"
[ 2490.268] compiled for 4.0.2, module version = 1.0.0
[ 2490.268] Module class: X.Org Server Extension
[ 2490.268] (II) NVIDIA GLX Module 346.47 Thu Feb 19 18:09:07 PST 2015
[ 2490.268] (II) LoadModule: "nvidia"
[ 2490.268] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 2490.269] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 2490.269] compiled for 4.0.2, module version = 1.0.0
[ 2490.269] Module class: X.Org Video Driver
[ 2490.269] (II) NVIDIA dlloader X Driver 346.47 Thu Feb 19 17:47:18 PST 2015
[ 2490.269] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 2490.269] (++) using VT number 1
[ 2490.269] (--) controlling tty is VT number 1, auto-enabling KeepTty
[ 2490.269] (II) Loading sub module "fb"
[ 2490.269] (II) LoadModule: "fb"
[ 2490.269] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 2490.269] (II) Module fb: vendor="X.Org Foundation"
[ 2490.269] compiled for 1.17.1, module version = 1.0.0
[ 2490.269] ABI class: X.Org ANSI C Emulation, version 0.4
[ 2490.269] (II) Loading sub module "wfb"
[ 2490.269] (II) LoadModule: "wfb"
[ 2490.270] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 2490.270] (II) Module wfb: vendor="X.Org Foundation"
[ 2490.270] compiled for 1.17.1, module version = 1.0.0
[ 2490.270] ABI class: X.Org ANSI C Emulation, version 0.4
[ 2490.270] (II) Loading sub module "ramdac"
[ 2490.270] (II) LoadModule: "ramdac"
[ 2490.270] (II) Module "ramdac" already built-in
[ 2490.270] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 2490.270] (==) NVIDIA(0): RGB weight 888
[ 2490.270] (==) NVIDIA(0): Default visual is TrueColor
[ 2490.270] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 2490.270] (**) NVIDIA(0): Option "Stereo" "0"
[ 2490.270] (**) NVIDIA(0): Option "SLI" "Off"
[ 2490.270] (**) NVIDIA(0): Option "MultiGPU" "Off"
[ 2490.270] (**) NVIDIA(0): Option "BaseMosaic" "off"
[ 2490.270] (**) NVIDIA(0): Stereo disabled by request
[ 2490.270] (**) NVIDIA(0): NVIDIA SLI disabled.
[ 2490.270] (**) NVIDIA(0): NVIDIA Multi-GPU disabled.
[ 2490.271] (**) NVIDIA(0): Option "MetaModes" "DVI-I-1: nvidia-auto-select +1280+0, DVI-D-0: nvidia-auto-select +0+416"
[ 2490.271] (**) NVIDIA(0): Enabling 2D acceleration
[ 2490.690] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20150116)
[ 2490.692] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 680 (GK104) at PCI:1:0:0 (GPU-0)
[ 2490.692] (--) NVIDIA(0): Memory: 2097152 kBytes
[ 2490.692] (--) NVIDIA(0): VideoBIOS: 80.04.09.00.01
[ 2490.692] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 2490.709] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 680 at PCI:1:0:0
[ 2490.709] (--) NVIDIA(0): CRT-0
[ 2490.709] (--) NVIDIA(0): Samsung SMS27A850T (DFP-0) (boot, connected)
[ 2490.709] (--) NVIDIA(0): DFP-1
[ 2490.709] (--) NVIDIA(0): DFP-2
[ 2490.709] (--) NVIDIA(0): Samsung SyncMaster (DFP-3) (connected)
[ 2490.709] (--) NVIDIA(0): DFP-4
[ 2490.709] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[ 2490.710] (--) NVIDIA(0): Samsung SMS27A850T (DFP-0): Internal TMDS
[ 2490.710] (--) NVIDIA(GPU-0): Samsung SMS27A850T (DFP-0): 330.0 MHz maximum pixel clock
[ 2490.710] (--) NVIDIA(0): DFP-1: Internal TMDS
[ 2490.710] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[ 2490.710] (--) NVIDIA(0): DFP-2: Internal TMDS
[ 2490.710] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[ 2490.710] (--) NVIDIA(0): Samsung SyncMaster (DFP-3): Internal TMDS
[ 2490.710] (--) NVIDIA(GPU-0): Samsung SyncMaster (DFP-3): 330.0 MHz maximum pixel clock
[ 2490.710] (--) NVIDIA(0): DFP-4: Internal DisplayPort
[ 2490.710] (--) NVIDIA(GPU-0): DFP-4: 960.0 MHz maximum pixel clock
[ 2490.710] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 2490.710] (**) NVIDIA(0): device Samsung SMS27A850T (DFP-0) (Using EDID frequencies
[ 2490.710] (**) NVIDIA(0): has been enabled on all display devices.)
[ 2490.710] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850T (DFP-0) contradicts itself:
[ 2490.710] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
[ 2490.710] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 2490.710] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 2490.710] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
[ 2490.710] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850T (DFP-0) contradicts itself:
[ 2490.710] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
[ 2490.710] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 2490.710] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 2490.710] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
[ 2490.710] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850T (DFP-0) contradicts itself:
[ 2490.710] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
[ 2490.710] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 2490.710] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 2490.710] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
[ 2490.712] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 2490.712] (**) NVIDIA(0): device Samsung SyncMaster (DFP-3) (Using EDID frequencies
[ 2490.712] (**) NVIDIA(0): has been enabled on all display devices.)
[ 2490.713] (II) NVIDIA(0): Validated MetaModes:
[ 2490.713] (II) NVIDIA(0):
[ 2490.713] (II) NVIDIA(0): "DVI-I-1:nvidia-auto-select+1280+0,DVI-D-0:nvidia-auto-select+0+416"
[ 2490.713] (II) NVIDIA(0): Virtual screen size determined to be 3840 x 1440
[ 2490.742] (--) NVIDIA(0): DPI set to (125, 114); computed from "UseEdidDpi" X config
[ 2490.742] (--) NVIDIA(0): option
[ 2490.742] (--) Depth 24 pixmap format is 32 bpp
[ 2490.743] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 2490.743] (II) NVIDIA: access.
[ 2490.746] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 2490.746] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 2490.746] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 2490.746] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 2490.746] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 2490.746] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 2490.746] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 2490.746] (II) NVIDIA(0): Config Options in the README.
[ 2490.761] (II) NVIDIA(0): Setting mode "DVI-I-1:nvidia-auto-select+1280+0,DVI-D-0:nvidia-auto-select+0+416"
[ 2490.853] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 2490.853] (==) NVIDIA(0): Backing store enabled
[ 2490.853] (==) NVIDIA(0): Silken mouse enabled
[ 2490.853] (**) NVIDIA(0): DPMS enabled
[ 2490.853] (II) Loading sub module "dri2"
[ 2490.853] (II) LoadModule: "dri2"
[ 2490.853] (II) Module "dri2" already built-in
[ 2490.853] (II) NVIDIA(0): [DRI2] Setup complete
[ 2490.853] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 2490.853] (--) RandR disabled
[ 2490.856] (II) Initializing extension GLX
[ 2490.856] (II) Indirect GLX disabled.(II) config/udev: Adding input device Power Button (/dev/input/event7)
[ 2490.914] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 2490.914] (**) Power Button: Applying InputClass "Keyboard Defaults"
[ 2490.914] (II) LoadModule: "evdev"
[ 2490.914] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 2490.914] (II) Module evdev: vendor="X.Org Foundation"
[ 2490.914] compiled for 1.17.1, module version = 2.9.2
[ 2490.914] Module class: X.Org XInput Driver
[ 2490.914] ABI class: X.Org XInput driver, version 21.0
[ 2490.915] (II) systemd-logind: got fd for /dev/input/event7 13:71 fd 30 paused 0
[ 2490.915] (II) Using input driver 'evdev' for 'Power Button'
[ 2490.915] (**) Power Button: always reports core events
[ 2490.915] (**) evdev: Power Button: Device: "/dev/input/event7"
[ 2490.915] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 2490.915] (--) evdev: Power Button: Found keys
[ 2490.915] (II) evdev: Power Button: Configuring as keyboard
[ 2490.915] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input9/event7"
[ 2490.915] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 2490.915] (**) Option "xkb_rules" "evdev"
[ 2490.915] (**) Option "xkb_model" "pc104"
[ 2490.915] (**) Option "xkb_layout" "us"
[ 2490.915] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 2490.940] (II) config/udev: Adding input device Power Button (/dev/input/event6)
[ 2490.940] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 2490.940] (**) Power Button: Applying InputClass "Keyboard Defaults"
[ 2490.941] (II) systemd-logind: got fd for /dev/input/event6 13:70 fd 31 paused 0
[ 2490.941] (II) Using input driver 'evdev' for 'Power Button'
[ 2490.941] (**) Power Button: always reports core events
[ 2490.941] (**) evdev: Power Button: Device: "/dev/input/event6"
[ 2490.941] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 2490.941] (--) evdev: Power Button: Found keys
[ 2490.941] (II) evdev: Power Button: Configuring as keyboard
[ 2490.941] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input8/event6"
[ 2490.941] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 2490.941] (**) Option "xkb_rules" "evdev"
[ 2490.941] (**) Option "xkb_model" "pc104"
[ 2490.941] (**) Option "xkb_layout" "us"
[ 2490.941] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 2490.942] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event18)
[ 2490.942] (II) No input driver specified, ignoring this device.
[ 2490.942] (II) This device may have been added with another device file.
[ 2490.942] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event19)
[ 2490.942] (II) No input driver specified, ignoring this device.
[ 2490.942] (II) This device may have been added with another device file.
[ 2490.942] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event20)
[ 2490.942] (II) No input driver specified, ignoring this device.
[ 2490.942] (II) This device may have been added with another device file.
[ 2490.942] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event21)
[ 2490.942] (II) No input driver specified, ignoring this device.
[ 2490.942] (II) This device may have been added with another device file.
[ 2490.942] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event10)
[ 2490.942] (II) No input driver specified, ignoring this device.
[ 2490.942] (II) This device may have been added with another device file.
[ 2490.943] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event11)
[ 2490.943] (II) No input driver specified, ignoring this device.
[ 2490.943] (II) This device may have been added with another device file.
[ 2490.943] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event12)
[ 2490.943] (II) No input driver specified, ignoring this device.
[ 2490.943] (II) This device may have been added with another device file.
[ 2490.943] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event13)
[ 2490.943] (II) No input driver specified, ignoring this device.
[ 2490.943] (II) This device may have been added with another device file.
[ 2490.943] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event14)
[ 2490.943] (II) No input driver specified, ignoring this device.
[ 2490.943] (II) This device may have been added with another device file.
[ 2490.943] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event15)
[ 2490.943] (II) No input driver specified, ignoring this device.
[ 2490.943] (II) This device may have been added with another device file.
[ 2490.943] (II) config/udev: Adding input device HDA Intel PCH Line Out Side (/dev/input/event16)
[ 2490.943] (II) No input driver specified, ignoring this device.
[ 2490.943] (II) This device may have been added with another device file.
[ 2490.944] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event17)
[ 2490.944] (II) No input driver specified, ignoring this device.
[ 2490.944] (II) This device may have been added with another device file.
[ 2490.944] (II) config/udev: Adding input device HID 1017:0002 (/dev/input/event0)
[ 2490.944] (**) HID 1017:0002: Applying InputClass "evdev keyboard catchall"
[ 2490.944] (**) HID 1017:0002: Applying InputClass "Keyboard Defaults"
[ 2490.944] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 32 paused 0
[ 2490.944] (II) Using input driver 'evdev' for 'HID 1017:0002'
[ 2490.944] (**) HID 1017:0002: always reports core events
[ 2490.944] (**) evdev: HID 1017:0002: Device: "/dev/input/event0"
[ 2490.945] (--) evdev: HID 1017:0002: Vendor 0x1017 Product 0x2
[ 2490.945] (--) evdev: HID 1017:0002: Found keys
[ 2490.945] (II) evdev: HID 1017:0002: Configuring as keyboard
[ 2490.945] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1c.1/0000:06:00.0/usb2/2-1/2-1:1.0/0003:1017:0002.0001/input/input2/event0"
[ 2490.945] (II) XINPUT: Adding extended input device "HID 1017:0002" (type: KEYBOARD, id 8)
[ 2490.945] (**) Option "xkb_rules" "evdev"
[ 2490.945] (**) Option "xkb_model" "pc104"
[ 2490.945] (**) Option "xkb_layout" "us"
[ 2490.945] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 2490.945] (II) config/udev: Adding input device HID 1017:0002 (/dev/input/event1)
[ 2490.945] (**) HID 1017:0002: Applying InputClass "evdev pointer catchall"
[ 2490.945] (**) HID 1017:0002: Applying InputClass "evdev keyboard catchall"
[ 2490.945] (**) HID 1017:0002: Applying InputClass "Keyboard Defaults"
[ 2490.946] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 33 paused 0
[ 2490.946] (II) Using input driver 'evdev' for 'HID 1017:0002'
[ 2490.946] (**) HID 1017:0002: always reports core events
[ 2490.946] (**) evdev: HID 1017:0002: Device: "/dev/input/event1"
[ 2490.946] (--) evdev: HID 1017:0002: Vendor 0x1017 Product 0x2
[ 2490.946] (--) evdev: HID 1017:0002: Found 9 mouse buttons
[ 2490.946] (--) evdev: HID 1017:0002: Found scroll wheel(s)
[ 2490.946] (--) evdev: HID 1017:0002: Found relative axes
[ 2490.946] (--) evdev: HID 1017:0002: Found x and y relative axes
[ 2490.946] (--) evdev: HID 1017:0002: Found absolute axes
[ 2490.946] (II) evdev: HID 1017:0002: Forcing absolute x/y axes to exist.
[ 2490.946] (--) evdev: HID 1017:0002: Found keys
[ 2490.946] (II) evdev: HID 1017:0002: Configuring as mouse
[ 2490.946] (II) evdev: HID 1017:0002: Configuring as keyboard
[ 2490.946] (II) evdev: HID 1017:0002: Adding scrollwheel support
[ 2490.946] (**) evdev: HID 1017:0002: YAxisMapping: buttons 4 and 5
[ 2490.946] (**) evdev: HID 1017:0002: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 2490.946] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1c.1/0000:06:00.0/usb2/2-1/2-1:1.1/0003:1017:0002.0002/input/input3/event1"
[ 2490.946] (II) XINPUT: Adding extended input device "HID 1017:0002" (type: KEYBOARD, id 9)
[ 2490.946] (**) Option "xkb_rules" "evdev"
[ 2490.946] (**) Option "xkb_model" "pc104"
[ 2490.946] (**) Option "xkb_layout" "us"
[ 2490.946] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 2490.946] (II) evdev: HID 1017:0002: initialized for relative axes.
[ 2490.946] (WW) evdev: HID 1017:0002: ignoring absolute axes.
[ 2490.946] (**) HID 1017:0002: (accel) keeping acceleration scheme 1
[ 2490.946] (**) HID 1017:0002: (accel) acceleration profile 0
[ 2490.946] (**) HID 1017:0002: (accel) acceleration factor: 2.000
[ 2490.946] (**) HID 1017:0002: (accel) acceleration threshold: 4
[ 2490.946] (II) config/udev: Adding input device HID 1017:0002 (/dev/input/mouse0)
[ 2490.946] (**) HID 1017:0002: Applying InputClass "Keyboard Defaults"
[ 2490.946] (II) No input driver specified, ignoring this device.
[ 2490.947] (II) This device may have been added with another device file.
[ 2490.947] (II) config/udev: Adding input device Logitech G9x Laser Mouse (/dev/input/event2)
[ 2490.947] (**) Logitech G9x Laser Mouse: Applying InputClass "evdev pointer catchall"
[ 2490.947] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 34 paused 0
[ 2490.947] (II) Using input driver 'evdev' for 'Logitech G9x Laser Mouse'
[ 2490.947] (**) Logitech G9x Laser Mouse: always reports core events
[ 2490.947] (**) evdev: Logitech G9x Laser Mouse: Device: "/dev/input/event2"
[ 2490.947] (--) evdev: Logitech G9x Laser Mouse: Vendor 0x46d Product 0xc066
[ 2490.947] (--) evdev: Logitech G9x Laser Mouse: Found 20 mouse buttons
[ 2490.947] (--) evdev: Logitech G9x Laser Mouse: Found scroll wheel(s)
[ 2490.947] (--) evdev: Logitech G9x Laser Mouse: Found relative axes
[ 2490.947] (--) evdev: Logitech G9x Laser Mouse: Found x and y relative axes
[ 2490.947] (II) evdev: Logitech G9x Laser Mouse: Configuring as mouse
[ 2490.947] (II) evdev: Logitech G9x Laser Mouse: Adding scrollwheel support
[ 2490.947] (**) evdev: Logitech G9x Laser Mouse: YAxisMapping: buttons 4 and 5
[ 2490.947] (**) evdev: Logitech G9x Laser Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 2490.947] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1c.3/0000:07:00.0/usb5/5-1/5-1.3/5-1.3:1.0/0003:046D:C066.0003/input/input4/event2"
[ 2490.947] (II) XINPUT: Adding extended input device "Logitech G9x Laser Mouse" (type: MOUSE, id 10)
[ 2490.947] (II) evdev: Logitech G9x Laser Mouse: initialized for relative axes.
[ 2490.948] (**) Logitech G9x Laser Mouse: (accel) keeping acceleration scheme 1
[ 2490.948] (**) Logitech G9x Laser Mouse: (accel) acceleration profile 0
[ 2490.948] (**) Logitech G9x Laser Mouse: (accel) acceleration factor: 2.000
[ 2490.948] (**) Logitech G9x Laser Mouse: (accel) acceleration threshold: 4
[ 2490.948] (II) config/udev: Adding input device Logitech G9x Laser Mouse (/dev/input/mouse1)
[ 2490.948] (II) No input driver specified, ignoring this device.
[ 2490.948] (II) This device may have been added with another device file.
[ 2490.948] (II) config/udev: Adding input device Logitech G9x Laser Mouse (/dev/input/event3)
[ 2490.948] (**) Logitech G9x Laser Mouse: Applying InputClass "evdev keyboard catchall"
[ 2490.948] (**) Logitech G9x Laser Mouse: Applying InputClass "Keyboard Defaults"
[ 2490.949] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 35 paused 0
[ 2490.949] (II) Using input driver 'evdev' for 'Logitech G9x Laser Mouse'
[ 2490.949] (**) Logitech G9x Laser Mouse: always reports core events
[ 2490.949] (**) evdev: Logitech G9x Laser Mouse: Device: "/dev/input/event3"
[ 2490.949] (--) evdev: Logitech G9x Laser Mouse: Vendor 0x46d Product 0xc066
[ 2490.949] (--) evdev: Logitech G9x Laser Mouse: Found 1 mouse buttons
[ 2490.949] (--) evdev: Logitech G9x Laser Mouse: Found scroll wheel(s)
[ 2490.949] (--) evdev: Logitech G9x Laser Mouse: Found relative axes
[ 2490.949] (II) evdev: Logitech G9x Laser Mouse: Forcing relative x/y axes to exist.
[ 2490.949] (--) evdev: Logitech G9x Laser Mouse: Found absolute axes
[ 2490.949] (II) evdev: Logitech G9x Laser Mouse: Forcing absolute x/y axes to exist.
[ 2490.949] (--) evdev: Logitech G9x Laser Mouse: Found keys
[ 2490.949] (II) evdev: Logitech G9x Laser Mouse: Configuring as mouse
[ 2490.949] (II) evdev: Logitech G9x Laser Mouse: Configuring as keyboard
[ 2490.949] (II) evdev: Logitech G9x Laser Mouse: Adding scrollwheel support
[ 2490.949] (**) evdev: Logitech G9x Laser Mouse: YAxisMapping: buttons 4 and 5
[ 2490.949] (**) evdev: Logitech G9x Laser Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 2490.949] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1c.3/0000:07:00.0/usb5/5-1/5-1.3/5-1.3:1.1/0003:046D:C066.0004/input/input5/event3"
[ 2490.949] (II) XINPUT: Adding extended input device "Logitech G9x Laser Mouse" (type: KEYBOARD, id 11)
[ 2490.949] (**) Option "xkb_rules" "evdev"
[ 2490.949] (**) Option "xkb_model" "pc104"
[ 2490.949] (**) Option "xkb_layout" "us"
[ 2490.949] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 2490.949] (II) evdev: Logitech G9x Laser Mouse: initialized for relative axes.
[ 2490.949] (WW) evdev: Logitech G9x Laser Mouse: ignoring absolute axes.
[ 2490.949] (**) Logitech G9x Laser Mouse: (accel) keeping acceleration scheme 1
[ 2490.949] (**) Logitech G9x Laser Mouse: (accel) acceleration profile 0
[ 2490.949] (**) Logitech G9x Laser Mouse: (accel) acceleration factor: 2.000
[ 2490.949] (**) Logitech G9x Laser Mouse: (accel) acceleration threshold: 4
[ 2490.949] (II) config/udev: Adding input device USB Keyboard (/dev/input/event4)
[ 2490.949] (**) USB Keyboard: Applying InputClass "evdev keyboard catchall"
[ 2490.949] (**) USB Keyboard: Applying InputClass "Keyboard Defaults"
[ 2490.950] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 36 paused 0
[ 2490.950] (II) Using input driver 'evdev' for 'USB Keyboard'
[ 2490.950] (**) USB Keyboard: always reports core events
[ 2490.950] (**) evdev: USB Keyboard: Device: "/dev/input/event4"
[ 2490.950] (--) evdev: USB Keyboard: Vendor 0x4d9 Product 0x274
[ 2490.950] (--) evdev: USB Keyboard: Found keys
[ 2490.950] (II) evdev: USB Keyboard: Configuring as keyboard
[ 2490.950] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1c.3/0000:07:00.0/usb5/5-1/5-1.4/5-1.4:1.0/0003:04D9:0274.0005/input/input6/event4"
[ 2490.950] (II) XINPUT: Adding extended input device "USB Keyboard" (type: KEYBOARD, id 12)
[ 2490.950] (**) Option "xkb_rules" "evdev"
[ 2490.950] (**) Option "xkb_model" "pc104"
[ 2490.950] (**) Option "xkb_layout" "us"
[ 2490.950] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 2490.951] (II) config/udev: Adding input device USB Keyboard (/dev/input/event5)
[ 2490.951] (**) USB Keyboard: Applying InputClass "evdev keyboard catchall"
[ 2490.951] (**) USB Keyboard: Applying InputClass "Keyboard Defaults"
[ 2490.951] (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 37 paused 0
[ 2490.951] (II) Using input driver 'evdev' for 'USB Keyboard'
[ 2490.951] (**) USB Keyboard: always reports core events
[ 2490.951] (**) evdev: USB Keyboard: Device: "/dev/input/event5"
[ 2490.951] (--) evdev: USB Keyboard: Vendor 0x4d9 Product 0x274
[ 2490.951] (--) evdev: USB Keyboard: Found 1 mouse buttons
[ 2490.951] (--) evdev: USB Keyboard: Found scroll wheel(s)
[ 2490.951] (--) evdev: USB Keyboard: Found relative axes
[ 2490.951] (II) evdev: USB Keyboard: Forcing relative x/y axes to exist.
[ 2490.951] (--) evdev: USB Keyboard: Found absolute axes
[ 2490.951] (II) evdev: USB Keyboard: Forcing absolute x/y axes to exist.
[ 2490.951] (--) evdev: USB Keyboard: Found keys
[ 2490.951] (II) evdev: USB Keyboard: Configuring as mouse
[ 2490.951] (II) evdev: USB Keyboard: Configuring as keyboard
[ 2490.951] (II) evdev: USB Keyboard: Adding scrollwheel support
[ 2490.951] (**) evdev: USB Keyboard: YAxisMapping: buttons 4 and 5
[ 2490.951] (**) evdev: USB Keyboard: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 2490.951] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1c.3/0000:07:00.0/usb5/5-1/5-1.4/5-1.4:1.1/0003:04D9:0274.0006/input/input7/event5"
[ 2490.951] (II) XINPUT: Adding extended input device "USB Keyboard" (type: KEYBOARD, id 13)
[ 2490.951] (**) Option "xkb_rules" "evdev"
[ 2490.951] (**) Option "xkb_model" "pc104"
[ 2490.951] (**) Option "xkb_layout" "us"
[ 2490.951] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 2490.952] (II) evdev: USB Keyboard: initialized for relative axes.
[ 2490.952] (WW) evdev: USB Keyboard: ignoring absolute axes.
[ 2490.952] (**) USB Keyboard: (accel) keeping acceleration scheme 1
[ 2490.952] (**) USB Keyboard: (accel) acceleration profile 0
[ 2490.952] (**) USB Keyboard: (accel) acceleration factor: 2.000
[ 2490.952] (**) USB Keyboard: (accel) acceleration threshold: 4
[ 2490.952] (II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event9)
[ 2490.952] (**) Eee PC WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[ 2490.952] (**) Eee PC WMI hotkeys: Applying InputClass "Keyboard Defaults"
[ 2490.952] (II) systemd-logind: got fd for /dev/input/event9 13:73 fd 38 paused 0
[ 2490.952] (II) Using input driver 'evdev' for 'Eee PC WMI hotkeys'
[ 2490.952] (**) Eee PC WMI hotkeys: always reports core events
[ 2490.952] (**) evdev: Eee PC WMI hotkeys: Device: "/dev/input/event9"
[ 2490.953] (--) evdev: Eee PC WMI hotkeys: Vendor 0 Product 0
[ 2490.953] (--) evdev: Eee PC WMI hotkeys: Found keys
[ 2490.953] (II) evdev: Eee PC WMI hotkeys: Configuring as keyboard
[ 2490.953] (**) Option "config_info" "udev:/sys/devices/platform/eeepc-wmi/input/input12/event9"
[ 2490.953] (II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 14)
[ 2490.953] (**) Option "xkb_rules" "evdev"
[ 2490.953] (**) Option "xkb_model" "pc104"
[ 2490.953] (**) Option "xkb_layout" "us"
[ 2490.953] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 2490.953] (II) config/udev: Adding input device PC Speaker (/dev/input/event8)
[ 2490.953] (II) No input driver specified, ignoring this device.
[ 2490.953] (II) This device may have been added with another device file.
[ 2491.022] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 2491.022] (**) NVIDIA(0): device Samsung SyncMaster (DFP-3) (Using EDID frequencies
[ 2491.022] (**) NVIDIA(0): has been enabled on all display devices.)
[ 2491.034] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 2491.034] (**) NVIDIA(0): device Samsung SMS27A850T (DFP-0) (Using EDID frequencies
[ 2491.034] (**) NVIDIA(0): has been enabled on all display devices.)
[ 2491.034] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850T (DFP-0) contradicts itself:
[ 2491.034] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
[ 2491.034] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 2491.034] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 2491.034] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
[ 2491.034] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850T (DFP-0) contradicts itself:
[ 2491.034] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
[ 2491.034] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 2491.034] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 2491.034] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
[ 2491.034] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850T (DFP-0) contradicts itself:
[ 2491.034] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
[ 2491.034] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 2491.034] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 2491.034] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
Last edited by H3g3m0n (2015-04-01 00:11:52)WonderWoofy wrote:I'm not sure about your VT issue, but if you set the 'terminate:ctrl_alt_bksp' option with setxkbmap or loginctl, does it work then?
I tried setxkbmap before without success.
Also tried:
localectl set-x11-keymap "us" "" "" "terminate:ctrl_alt_bksp"
Not sure how to go about using loginctl to do the same thing.
Last edited by H3g3m0n (2015-04-01 03:25:35) -
Brand spanking new installation of win XP. All updates done using IE.
Firewall and anti-virus installed.
Java 7 9 and Flash 10.3.183.10 installed
Everything is fine until...
Install Firefox 16.0.2
Start firefox
Go to Yahoo and open some news in new tabs
Mouse doesn't move, Alt-Tab does nothing, Ctrl-Alt-Del still nothing, Reset
restart crash restart crash restart use IE to come here and try to find why Firefox is now freezing my XPStart Firefox in <u>[[Safe Mode|Safe Mode]]</u> to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance).
*Do not click the Reset button on the Safe mode start window or otherwise make changes.
*https://support.mozilla.org/kb/Safe+Mode
*https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
See also:
*http://kb.mozillazine.org/Firefox_crashes
* http://kb.mozillazine.org/Firefox_hangs -
Ctrl+Alt+C Shortcut Problem in Indesign CS3
I cannot use the ctrl+alt+c shortcut in IdCS3. The alt key works with all other shortcuts. I believe this is caused by ATI's catalyst control center which uses the same shortcut to open it's window but I disabled the hotkeys in catalyst and even changed that hotkey to one besides ctrl+alt+c and I can still not get the shortcut to work in Id.
This happened to me about a year ago and I can't remember how I fixed it.
Thanks in advance for any help.I had this problem, Ctrl-Alt-C did not work in Indesign or Photoshop (but CS5.5 & Windows 7).
To fix it:
> right click your desktop background
> select catalyst Control Centre (top of list)
> ‘Options’ at top right pull down menu
(if you can’t see this, choose Advanced install, OK, then go back to step one again)
>Hotkeys > Hot Keys Manager
> select the one thing in the list, then press Edit
> Change from Ctrl+Alt+C to Ctrl+Alt+Shift+C
> OK, OK, OK
Hey presto! It’s all working now! -
Ctrl+alt delete in Windows XP. Where is Pause button?
How to do the ctrl+alt delete in Windows XP?
Where can I find the Pause button you see on regular keyboard?Search the Discussion Board using "ctrlaltdel" as the string. There are a number of possible solutions posted, including key remappers and external keyboards. kierrep posted the following answer earlier this month, and the questioner gave the post a star:
Try "input remapper" instead:
http://www.olofsson.info/
this programm is amazing for windows on a mac!
-it enables the fn-keys (for display brightnes and volume)
-the right click is the second enter key on your key board
-fn-eject works like print screen
-for contorl-alt-delte: fn-ctrl-alt-backspace (of course: delete = fn-backspace)
Just an advice: if you have problems or questions about boot camp, try http://forum.onmac.net/
It is a nice forum and almost every question has already been discussed there. Just use the search function.
Powerbook G4, iBook, MacBook, iMac, HP n6220 Mac OS X (10.4.7) -
Remote desktop ctrl+alt+delete
I need to be able to ctrl+alt+delete on something that is frozen on my remote desktop from my mac. If I use command + option + escape, it will force quite the remote desktop client but not the program that is running on my remote desktop that is frozen. Any suggestions?
Search the Discussion Board using "ctrlaltdel" as the string. There are a number of possible solutions posted, including key remappers and external keyboards. kierrep posted the following answer earlier this month, and the questioner gave the post a star:
Try "input remapper" instead:
http://www.olofsson.info/
this programm is amazing for windows on a mac!
-it enables the fn-keys (for display brightnes and volume)
-the right click is the second enter key on your key board
-fn-eject works like print screen
-for contorl-alt-delte: fn-ctrl-alt-backspace (of course: delete = fn-backspace)
Just an advice: if you have problems or questions about boot camp, try http://forum.onmac.net/
It is a nice forum and almost every question has already been discussed there. Just use the search function.
Powerbook G4, iBook, MacBook, iMac, HP n6220 Mac OS X (10.4.7) -
Ctrl/Alt click to activate link closes current document
We just upgraded from Framemaker 7.2 to 12, and there's a behavior I can't figure out. I have a book file with cross-references between FM documents. Before, in FM 7.2, when I used Ctrl/Alt+click to activate a cross-reference link and follow the marker to a different Frame document, it left the original document open, and also opened the document the link caused me to jump to. In FM 12, it is closing the original document every time I click on a link to follow it. Is there a preference setting or another way to stop Frame from closing the first document every time it opens the document the link is referencing?
Some of these resources might come in handy...They have illustrated workflows and embedded videos. For more assistance: [email protected] and [email protected]
1. 10-part blog series on reasons to upgrade from FM 7.x to FM 10: http://blogs.adobe.com/techcomm/2012/04/part-5-%C2%BD-reasons-to-upgrade-from-fm-7-x-to-fm -10-summary-thus-far.html
2. 8-part blog series on reasons to upgrade from FM 7.x to FM 11:
Part 1 - Part (1) Reasons to upgrade from FM 7.x to FM 11: Catalogs, UI, rich media and more « TechComm Central by Adobe
Part 2 - Part (2) Reasons to upgrade from FM 7.x to FM 11: Workspaces and a Friendlier UI « TechComm Central by Adobe
Part 3 - Part (3) Reasons to upgrade from FM 7.x to FM 11: Track changes and Import PDF comments « TechComm Central by Adobe
Part 4 - Part (4) Reasons to upgrade from FM 7.x to FM 11: Catalogs and Format Overrides « TechComm Central by Adobe
Part 5 - Part (5) Reasons to upgrade from FM 7.x to FM 11: Where were you in 2002? « TechComm Central by Adobe
Part 6 - Part (6) Reasons to upgrade from FM 7.x to FM 11: Book Building « TechComm Central by Adobe
Part 7 - Part (7) Reasons to upgrade from FM 7.x to FM 11: XML and Structured Editing « TechComm Central by Adobe
Part 8 - Part (8) Reasons to upgrade from FM 7.x to FM 11: “Real” support for DITA « TechComm Central by Adobe
3. 8-part blog series on reasons to upgrade from FM 7.x to FM 12.
Upgrade to FM12 INTRO: Overview of many reasons
http://blogs.adobe.com/techcomm/2014/06/why-upgrade-from-fm7-8-or-9-intro-overview-of-many -reasons.html
Upgrade to FM12 Reason #1) Fewer steps, more automation
http://blogs.adobe.com/techcomm/2014/06/why-upgrade-from-fm7-1-new-workflow-ui-powertools- more.html
Upgrade to FM12 Reason #2) Greater customization, customized workflows
http://blogs.adobe.com/techcomm/2014/07/why-upgrade-from-fm7-2-workspaces-productivity-too ls.html
Upgrade to FM12 Reason #3) Collaborative and Mobile Review
http://blogs.adobe.com/techcomm/2014/07/why-upgrade-from-fm7-8-or-9-3-review-cycle-with-mo bile-dropbox-and-cms.html
Upgrade to FM12 Reason #4) Fuller Format and structure control
http://blogs.adobe.com/techcomm/2014/07/why-upgrade-from-fm7-8-or-9-4.html
Upgrade to FM12 Reason #5) Tools for handling large projects
http://blogs.adobe.com/techcomm/2014/07/why-upgrade-from-fm7-8-or-9-5-book-building-and-ex ternal-references.html
Upgrade to FM12 Reason #6) Full DITA Compliance, Accessible Structured Editing
http://blogs.adobe.com/techcomm/2014/07/why-upgrade-from-fm7-8-or-9-6-xml-and-structured-e diting.html
Upgrade to FM12 Reason #7) Direct XML editing and low-cost FM XML Author
http://blogs.adobe.com/techcomm/2014/07/why-upgrade-from-fm7-8-or-9-7-real-ditaxml-authori ng-with-a-junior-version.html
Thanks,
Saibal -
Topic says it all...
My friend started a installation of Windows Vista, but pulled out after deleting all partitions...
So now i power it on, get a blank screen (seems a bit gray because of backlighting, should show the apple logo right?)...
Then after like 15-20sec it will throw out a:
BOOTMGR is missing
Press Ctrl+Alt+Del to restart
I have a OEM Windows Vista DVD in the drive, and i know... Windows 7 is better... but i'm not that fond of stealing software from Microsoft and i have 10 licenses for Vista...
I have tried pressing C while booting up but it doesn't work...
Does anyone here have a magic soloution for me, and no i will not install MacOS on it !!!Deleting Boot Camp partitions the conventional way will not work . You must use the Boot Camp Assistant to remove a Boot Camp partition. Here is a link to the guide.
http://manuals.info.apple.com/en_US/Boot_Camp_Install-Setup_10.6.pdf
The way to restart is to hold down the option/alt key during startup* and then selecting the Mac OS. If you have a valid Boot Camp install of Windows it would show up during this type of start up.
* hold down immediately after pressing the power button and until the OS choice screen appears.
To summarize.
1 Use the above method to boot into Mac OS.
2 Download the instructions and read them.
3 Use Boot Camp Assistant to remove the partition.
4 Pick your friends more carefully. -
Revolve 810 G1 Unlock Computer when in Tablet Mode. Press CTRL-ALT-DEL or Windows Security Button
1. I have an Revolve 810 G1
Running Windows 7 Pro (64 Bit).
When I change the screen to Tablet Mode
(Folding tablet over keyboard and using as tablet).
I lock my computer.
2. What to know how to unlock without having to Open back up and use the CTL-Alt-DEL keys.
When Locked screen shows: Press CTRL-ALT-DEL or use the Windows Security Button to unlock this computer.
I would like to use the Windows Button on the bottom of the screen
(One Used in Windows 8 to change between Desktop and Metro) to Unlock screen And bring up on screen keyboard to put in my password.
This is probably how it should work, but it does not work.
Even bringing up the onscreen keyboard via the blue power button On the screen to Ease Of Access does not work.
The CLT-ALT-DEL on the on screen keyboard will not unlock the screen.
P.S.
Where is that Windows Security Button when you need it?
Thanks,
RogIf you are using Windows 7 (not Windows 8), you should be able to touch the Ease of Access button at the lower left of the screen, then select Type without the keyboard (On-screen keyboard). When the on-screen keyboard pops-up, press CTRL, then ALT, then DEL. You should get a password prompt; the on-screen keyboard will stay visible unless and until you close it.
Although I am an HP employee, I am speaking for myself and not for HP.
Please click the little thumbs-up dealybopper to the lower right if my reply was helpful to you. Please mark Accept As Solution if it solves your problem. This will help others, too! -
Ctrl Alt Del and Task manager not working
Hi, Ive been having a problem getting task manager to run at all. On a fresh reboot, if I use the ctrl alt del function the according screen will come up like normal, and I will click on task manager. It bring me back to my desktop and nothing pops up.
Its not running in my task bar or anything. Then if I try to use the ctrl alt del function again, nothing happens. Ive tried running task manager straight from the start menu, but then I get an error saying that the version of that file is not compatible with
the version of windows I am running, which is 64 bit W7. It just started happening on my system a few days ago and I have changed nothing the past few days. I have tried to do a system restore, but to my idiocy, I did not know I needed to manually create restore
points. So I can only restore to yesterday which would fix nothing. I have run antivirus and anti spyware programs and they have shown no problems and my hard drive only has a 1% disk fragmentation. Is there a way to uninstall and re download a 64 bit compatible
version of the windows 7 task manager? Or is there a separate reason why it is not working? ThankyouAlso try it By Registry Editor :
Start --> Run --> regedit --> ok
Then
Hive: HKEY_CURRENT_USER
Key: Software\Microsoft\Windows\CurrentVersion\Policies\System
Name: DisableTaskMgr
Type: REG_DWORD
Value: 0=Disablethis key, that is Don't Disable, Enable TaskManager
Regards,
MCP | MCTS | MCITP
The first fix did not work, I tried doing the second one but there is no system folder in
Software\Microsoft\Windows\CurrentVersion\Policies\
The only one its showing is an explorer folder. -
Ctrl/Alt Keys not Working in Parallels
Hi,
I'm running Illustrator CS6 using Parallels Desktop 8 and Windows 7. It appears that the ctrl/alt keys do not work. Has anyone found a solution? I've tried resetting my preferences and restarting my computer. Any help would be greatly appreciaed.Although this is an old thread, I also seem to be having the same sort of issues with Illustrator CS2 in Snow Leopard running under Parallels Desktop 9.
Re. the proposed solution, there does not seem to be a 'Virtual Machine -> Configure -> Options -> Advanced -> Optimize modifier keys for games' option in Desktop 9 - or I've not found it.
I will pursue this in the Parallels forums, but if anyone here has found a solution, I'd be interested to hear it. -
This happens when FireFox is not responding, and I want to close firefox with ctrl-alt-delete. Too many tabs can make Firefox crash. That is why I want to use ctrl-alt-delete to close FireFox. I tried finding a way to disable this, but I found no option to.
Ending the Firefox program or process with the Windows Task Manager "looks like" a crash. The proper way to exit Firefox is click Firefox button > Exit (or File > Exit, if using the Menu Bar).
'''If this reply solves your problem, please click "Solved It" next to this reply when <u>signed-in</u> to the forum.'''
Not related to your question, but...
You need to update some plug-ins:
*Plug-in check: https://www-trunk.stage.mozilla.com/en-US/plugincheck/
*Adobe Shockwave for Director Netscape plug-in: [https://support.mozilla.com/en-US/kb/Using%20the%20Shockwave%20plugin%20with%20Firefox#w_installing-shockwave Installing ('''''or Updating''''') the Shockwave plugin with Firefox]
*Adobe PDF Plug-In For Firefox and Netscape: [https://support.mozilla.com/en-US/kb/Using%20the%20Adobe%20Reader%20plugin%20with%20Firefox#w_installing-and-updating-adobe-reader Installing/Updating Adobe Reader in Firefox]
*Shockwave Flash (Adobe Flash or Flash): [https://support.mozilla.com/en-US/kb/Managing%20the%20Flash%20plugin#w_updating-flash Updating Flash in Firefox]
*Next Generation Java Plug-in for Mozilla browsers: [https://support.mozilla.com/en-US/kb/Using%20the%20Java%20plugin%20with%20Firefox#w_installing-or-updating-java Installing or Updating Java in Firefox] -
What happens to a mail item, Fn-Ctrl-Alt-Del is pressed
What happens to a mail item, when Fn-Ctrl-Alt-Del is pressed while in the mail tool? I can't seem to find the email file anywhere.
Is there a way to disable this key pattern in the mail program?What happens to a mail item, when Fn-Ctrl-Alt-Del is pressed while in the mail tool? I can't seem to find the email file anywhere.
Looks to me like I permanently deletes the message.
Is there a way to disable this key pattern in the mail program?
Is this really a key combination you find it easy to press by mistake? To answer the question, no, it doesn't look like you can remap that, but note that if you choose Edit -> Undo immediately after deleting, the message will come back. -
I am having a problem with Firefox. Whenever I open it, it runs fine for about five seconds and then freezes. A small white rectangle appears in the upper left corner of the browser window. The screen still scrolls fine, but whenever I try clicking on anything (including the menus in the toolbar), it just gives me an unresponsive 'ding' sound. When I try closing the programme with Ctrl+alt+delete, I get a message saying 'The system cannot end this programme as it is waiting for a response from you'. I originally had this problem with an earlier version of Firefox and tried installing Firefox 4 to see if this helped. It worked for two days and began doing it again. I have already tried un- and re-installing Firefox and restarting my computer, and Firefox will not run properly for long enough to let me disable any add-ons or plug-ins. What can I do to fix this?
I've added a couple of screencaps of the problem. (or tried to)
[http://i53.tinypic.com/161hvh2.jpg The white rectangle]
[http://i51.tinypic.com/dwsq1.png Error message]Have also since found out that to start FF4 in safe mode you just hold shift whilst double-clicking the icon. We only find these things out after the event, murphy's law!
Maybe you are looking for
-
Not able to run installer when booting (Snow)Leopard on MacBook Pro Unibody
Hi all. I would very much appreciate any help with this issue... I have recently installed an app called monolingual(stay away from it - don't touch it with a stick) - I thought I'd get a couple of GBs off my HDD by deleting the surplus languages...
-
i think macrumors had mentioned that there would be some speed increases with rosetta in the new 10.4.8 update. anyone notice this MS word seems to be running pretty quick anyone notice any significant upgrades speed?
-
The video button does not activate on itunes when i connect the 30GB ipod
I have a 30GB ipod. when i connect it to the computer and start itunes, and go to the "ipod" tab, and then "video", after that, none of the video buttons are active (such as "actomatically update all videos"; "do not update videos" etc. I have the la
-
Business Packages for IS-U 4.64
Hello, my company will use the SAP portal for some applications and I am looking for the existing SAP Business Packages . On sdn I find a list of existing BP but I don't see any for IS-U 4.64 which is the kernel of our job. The BP for Key Account Man
-
Hello, I am trying to create a message from the SOLAR01 t-code. System creates the message and displays the following: Green Tick mark- Message <nn> created successfully in the system <SID>. Basis message not created. It does not give any error here.