Awesome + Shifty: clientbuttons don't work

Hi,
I'm playing around with awesome and installed shifty. Works fine, but the key-/buttonbindings for actions on client windows (modkey + rightclick = resize etc.) have seized to work. What could that be?
My rc.lua is posted below, apart from some keybindings it's mostly unchanged, I haven't even edited the example tag definition for Shifty yet :
-- {{{ Load libraries
require("awful")
require("awful.autofocus")
require("awful.rules")
require("beautiful")
require("naughty")
require("shifty")
-- {{{ Variable definitions
-- Themes define colours, icons, and wallpapers
beautiful.init(awful.util.getdir("config") .. "/themes/zenburn/theme.lua")
-- This is used later as the default terminal and editor to run.
terminal = "urxvt"
editor = os.getenv("EDITOR") or "nano"
editor_cmd = terminal .. " -e " .. editor
-- Default modkey.
modkey = "Mod4"
altkey = "Mod1"
-- Table of layouts to cover with awful.layout.inc, order matters.
-- Available layouts: awful.layout.suit.floating, .tile, .tile.left,
-- .tile.bottom, .tile.top, .fair, .fair.horizontal, .spiral,
-- .spiral.dwindle, .max, .max.fullscreen, .magnifier
layouts =
awful.layout.suit.floating,
awful.layout.suit.tile,
awful.layout.suit.tile.left,
awful.layout.suit.tile.bottom,
awful.layout.suit.tile.top,
awful.layout.suit.max,
awful.layout.suit.max.fullscreen,
-- {{{ Tags: Traditional way
-- Define a tag table which hold all screen tags.
tags = {
names = { 1, 2, 3, 4, 5, 6, 7, 8, 9 },
layout = { layouts[1], layouts[2], layouts[1], layouts[1],
layouts[1], layouts[1], layouts[1], layouts[1], layouts[1] }
for s = 1, screen.count() do
-- Each screen has its own tag table.
-- tags[s] = awful.tag({ 1, 2, 3, 4, 5, 6, 7, 8, 9 }, s, layouts[1])
tags[s] = awful.tag( tags.names, s, tags.layout)
end
-- {{{ Tags using Shifty
-- tag settings
shifty.config.tags =
["term"] = { position = 1, exclusive = true, spawn = terminal, },
["web"] = { position = 2, exclusive = true, spawn = browser, layout = awful.layout.suit.max, },
-- client settings
-- order here matters, early rules will be applied first
shifty.config.apps =
{ match = { "Navigator","Vimperator","Gran Paradiso","Firefox","Iceweasel","Opera"} , tag = "web" } ,
{ match = { "xterm", "urxvt"} , honorsizehints = false, slave = true, tag = "term" } ,
{ match = { "pcmanfm" }, slave = true } ,
{ match = { "" }, buttons =
button({ }, 1, function (c) client.focus = c; c:raise() end),
button({ modkey }, 1, function (c) awful.mouse.client.move() end),
button({ modkey }, 3, awful.mouse.client.resize ),
-- tag defaults
shifty.config.defaults =
layout = awful.layout.suit.tile.bottom,
ncol = 1,
mwfact = 0.60,
floatBars = true
shifty.init()
-- {{{ Menu
-- Create a laucher widget and a main menu
myawesomemenu =
{ "manual", terminal .. " -e man awesome" },
{ "edit config", editor_cmd .. " " .. awful.util.getdir("config") .. "/rc.lua" },
{ "restart", awesome.restart },
{ "quit", awesome.quit }
mymainmenu = awful.menu(
items =
{ "awesome", myawesomemenu, beautiful.awesome_icon },
{ "open terminal", terminal }
mylauncher = awful.widget.launcher(
image = image(beautiful.awesome_icon),
menu = mymainmenu
-- {{{ Wibox
-- Create a textclock widget
mytextclock = awful.widget.textclock({ align = "right" })
-- Create a systray
mysystray = widget({ type = "systray" })
-- Create a wibox for each screen and add it
mywibox = {}
mypromptbox = {}
mylayoutbox = {}
mytaglist = {}
mytaglist.buttons = awful.util.table.join(
awful.button({ }, 1, awful.tag.viewonly),
awful.button({ modkey }, 1, awful.client.movetotag),
awful.button({ }, 3, awful.tag.viewtoggle),
awful.button({ modkey }, 3, awful.client.toggletag),
awful.button({ }, 4, awful.tag.viewnext),
awful.button({ }, 5, awful.tag.viewprev)
mytasklist = {}
mytasklist.buttons = awful.util.table.join(
awful.button({ }, 1,
function (c)
if not c:isvisible() then
awful.tag.viewonly(c:tags()[1])
end
client.focus = c
c:raise()
end
awful.button({ }, 3,
function ()
if instance then
instance:hide()
instance = nil
else
instance = awful.menu.clients({ width=250 })
end
end
awful.button({ }, 4,
function ()
awful.client.focus.byidx(1)
if client.focus then client.focus:raise() end
end
awful.button({ }, 5,
function ()
awful.client.focus.byidx(-1)
if client.focus then client.focus:raise() end
end
for s = 1, screen.count() do
-- Create a promptbox for each screen
mypromptbox[s] = awful.widget.prompt({ layout = awful.widget.layout.horizontal.leftright })
-- Create an imagebox widget which will contains an icon indicating which layout we're using.
-- We need one layoutbox per screen.
mylayoutbox[s] = awful.widget.layoutbox(s)
mylayoutbox[s]:buttons(
awful.util.table.join(
awful.button({ }, 1, function () awful.layout.inc(layouts, 1) end),
awful.button({ }, 3, function () awful.layout.inc(layouts, -1) end),
awful.button({ }, 4, function () awful.layout.inc(layouts, 1) end),
awful.button({ }, 5, function () awful.layout.inc(layouts, -1) end)
-- Create a taglist widget
mytaglist[s] = awful.widget.taglist(s, awful.widget.taglist.label.all, mytaglist.buttons)
-- Create a tasklist widget
mytasklist[s] = awful.widget.tasklist(
function(c)
return awful.widget.tasklist.label.currenttags(c, s)
end,
mytasklist.buttons
-- Create the wibox
mywibox[s] = awful.wibox({ position = "top", screen = s })
-- Add widgets to the wibox - order matters
mywibox[s].widgets =
mylauncher,
mytaglist[s],
mypromptbox[s],
layout = awful.widget.layout.horizontal.leftright
mylayoutbox[s],
mytextclock,
s == 1 and mysystray or nil,
mytasklist[s],
layout = awful.widget.layout.horizontal.rightleft
end
shifty.taglist = mytaglist
-- {{{ Mouse bindings
root.buttons(
awful.util.table.join(
awful.button({ }, 3, function () mymainmenu:toggle() end),
awful.button({ }, 4, awful.tag.viewnext),
awful.button({ }, 5, awful.tag.viewprev)
-- {{{ Key bindings
globalkeys = awful.util.table.join(
-- Tag manipulation
awful.key({ "Control", altkey }, "Left", awful.tag.viewprev ),
awful.key({ "Control", altkey }, "Right", awful.tag.viewnext ),
awful.key({ "Control", altkey }, "Escape", awful.tag.history.restore ),
awful.key({ modkey }, "t", function() shifty.add({ rel_index = 1 }) end),
awful.key({ modkey, "Control" }, "t", function() shifty.add({ rel_index = 1, nopopup = true }) end),
awful.key({ modkey, "Shift" }, "r", shifty.rename),
awful.key({ modkey, "Shift" }, "w", shifty.del),
awful.key({ altkey, }, "Tab",
function ()
awful.client.focus.byidx( 1)
if client.focus then client.focus:raise() end
end
awful.key({ altkey, "Shift" }, "Tab",
function ()
awful.client.focus.byidx(-1)
if client.focus then client.focus:raise() end
end
awful.key({ modkey, }, "w", function () mymainmenu:show(true) end ),
-- Layout manipulation
awful.key({ modkey, }, "Tab", function () awful.client.swap.byidx(1) end ),
awful.key({ modkey, "Shift" }, "Tab", function () awful.client.swap.byidx(-1) end ),
awful.key({ "Control" }, "Tab", function () awful.screen.focus_relative(1) end ),
awful.key({ "Control", "Shift" }, "Tab", function () awful.screen.focus_relative(-1) end ),
awful.key({ modkey, }, "u", awful.client.urgent.jumpto ),
-- awful.key({ modkey, }, "Tab",
-- function ()
-- awful.client.focus.history.previous()
-- if client.focus then
-- client.focus:raise()
-- end
-- end),
-- Standard program
awful.key({ modkey, }, "Return", function () awful.util.spawn(terminal) end ),
awful.key({ modkey, "Control" }, "r", awesome.restart ),
awful.key({ modkey, "Shift" }, "q", awesome.quit ),
awful.key({ modkey, }, "l", function () awful.tag.incmwfact( 0.05) end ),
awful.key({ modkey, }, "h", function () awful.tag.incmwfact(-0.05) end ),
awful.key({ modkey, "Shift" }, "h", function () awful.tag.incnmaster( 1) end ),
awful.key({ modkey, "Shift" }, "l", function () awful.tag.incnmaster(-1) end ),
awful.key({ modkey, "Control" }, "h", function () awful.tag.incncol( 1) end ),
awful.key({ modkey, "Control" }, "l", function () awful.tag.incncol(-1) end ),
awful.key({ modkey, }, "space", function () awful.layout.inc(layouts, 1) end ),
awful.key({ modkey, "Shift" }, "space", function () awful.layout.inc(layouts, -1) end ),
-- Prompt
awful.key({ modkey }, "r", function () mypromptbox[mouse.screen]:run() end ),
awful.key({ modkey }, "x",
function ()
awful.prompt.run({ prompt = "Run Lua code: " },
mypromptbox[mouse.screen].widget,
awful.util.eval, nil,
awful.util.getdir("cache") .. "/history_eval")
end
clientkeys = awful.util.table.join(
awful.key({ modkey, }, "f", function (c) c.fullscreen = not c.fullscreen end ),
awful.key({ modkey, "Shift" }, "c", function (c) c:kill() end ),
awful.key({ modkey, "Control" }, "space", awful.client.floating.toggle ),
awful.key({ modkey, "Control" }, "Return", function (c) c:swap(awful.client.getmaster()) end ),
awful.key({ modkey, }, "o", awful.client.movetoscreen ),
awful.key({ modkey, "Shift" }, "r", function (c) c:redraw() end ),
awful.key({ modkey, }, "n", function (c) c.minimized = not c.minimized end ),
awful.key({ modkey, }, "m",
function (c)
c.maximized_horizontal = not c.maximized_horizontal
c.maximized_vertical = not c.maximized_vertical
end
-- Compute the maximum number of digit we need, limited to 9
keynumber = 0
for s = 1, screen.count() do
keynumber = math.min(9, math.max(#tags[s], keynumber));
end
-- Bind all key numbers to tags.
-- Be careful: we use keycodes to make it works on any keyboard layout.
-- This should map on the top row of your keyboard, usually 1 to 9.
for i = 1, keynumber do
globalkeys = awful.util.table.join(
globalkeys, awful.key({ modkey }, "#" .. i + 9,
function ()
local screen = mouse.screen
if tags[screen][i] then
awful.tag.viewonly(tags[screen][i])
end
end
awful.key({ modkey, "Control" }, "#" .. i + 9,
function ()
local screen = mouse.screen
if tags[screen][i] then
awful.tag.viewtoggle(tags[screen][i])
end
end
awful.key({ modkey, "Shift" }, "#" .. i + 9,
function ()
if client.focus and tags[client.focus.screen][i] then
awful.client.movetotag(tags[client.focus.screen][i])
end
end
awful.key({ modkey, "Control", "Shift" }, "#" .. i + 9,
function ()
if client.focus and tags[client.focus.screen][i] then
awful.client.toggletag(tags[client.focus.screen][i])
end
end
end]]
-- Create <modkey>+i keybindings for Shifty
for i = 1, 9 do
globalkeys = awful.util.table.join(globalkeys,
awful.key(
{ modkey }, i,
function ()
local t = awful.tag.viewonly(shifty.getpos(i))
end
globalkeys = awful.util.table.join(globalkeys,
awful.key(
{ modkey, "Control" }, i,
function ()
local t = shifty.getpos(i)
t.selected = not t.selected
end
globalkeys = awful.util.table.join(globalkeys,
awful.key(
{ modkey, "Control", "Shift" }, i,
function ()
if client.focus then
awful.client.toggletag(shifty.getpos(i))
end
end
-- move clients to other tags
globalkeys = awful.util.table.join(globalkeys,
awful.key({ modkey, "Shift" }, i,
function ()
if client.focus then
local t = shifty.getpos(i)
awful.client.movetotag(t)
awful.tag.viewonly(t)
end
end
end
clientbuttons = awful.util.table.join(
awful.button({ }, 1, function (c) client.focus = c; c:raise() end),
awful.button({ altkey }, 1, awful.mouse.client.move),
awful.button({ altkey }, 3, awful.mouse.client.resize))
-- Set keys
root.keys(globalkeys)
shifty.config.globalkeys = globalkeys
shifty.config.clientkeys = clientkeys
--shifty.config.clientbuttons = clientbuttons
-- {{{ Rules
awful.rules.rules =
-- All clients will match this rule.
{ rule = { }, properties =
border_width = beautiful.border_width,
border_color = beautiful.border_normal,
focus = true,
keys = clientkeys,
buttons = clientbuttons
-- { rule = {class = "MPlayer" },
-- properties = { floating = true } },
-- { rule = { class = "pinentry" },
-- properties = { floating = true } },
-- { rule = { class = "gimp" },
-- properties = { floating = true } },
-- { rule = { class = "Pidgin", role = "buddy_list" },
-- properties = { tag = { tags[1][2], tags[1][3] } } },
-- { rule = { class = "Pidgin", role = "conversation" },
-- properties = { tag = { tags[1][3] } } },
-- { rule = { class = "Opera" },
--§ properties = { tag = tags[1][2] } }
-- {{{ Signals
-- Signal function to execute when a new client appears.
client.add_signal("manage",
function (c, startup)
-- Add a titlebar
-- awful.titlebar.add(c, { modkey = modkey })
-- Enable sloppy focus
c:add_signal("mouse::enter",
function(c)
if awful.layout.get(c.screen) ~= awful.layout.suit.magnifier
and awful.client.focus.filter(c) then
client.focus = c
end
end
if not startup then
-- Set the windows at the slave,
-- i.e. put it at the end of others instead of setting it master.
-- awful.client.setslave(c)
-- Put windows in a smart way, only if they does not set an initial position.
if not c.size_hints.user_position and not c.size_hints.program_position then
awful.placement.no_overlap(c)
awful.placement.no_offscreen(c)
end
end
end
client.add_signal("focus", function(c) c.border_color = beautiful.border_focus end)
client.add_signal("unfocus", function(c) c.border_color = beautiful.border_normal end)
Another question: Does anyone know a good awesome tutorial? Because the awesome wiki is rather useless, I'm afraid.

For Shifty it's in the shifty.config.apps section:
shifty.config.apps =
{ match = { "" }, buttons =
button({ }, 1, function (c) client.focus = c; c:raise() end),
button({ modkey }, 1, function (c) awful.mouse.client.move() end),
button({ modkey }, 3, awful.mouse.client.resize ),
but for some reason this does not work. But maybe it's to do with this being a set again later by awful in rules.rules. I'll play with that when I get home.
Concerning the wiki: Granted 'useless' was maybe too harsh, but the wiki is bad, including the tutorial, especially where the rules-table is concerned.
Example: Set up a rule to put a client on multiple tags by default. I find some entry somewhere (and I mean "some entry, somewhere". I can't even find it again, it is that well hidden) that tells me how to set 1 tag and mentions that I can set multiple tags "that way" as well. It doesn't tell me how, and a chance look in the correct place of the FAQ tells me that you CAN'T set multiple tags like you would set one, but have to use some strange function in conjunction with "callback =". Why? Because, apparently. The awesome-3-configuration entry doesn't even mention rules, neither does the tutorial.
If I wanted to teach awesome to cook tea, it would be alright for the wiki to be unhelpful, but the above seems to me to be pretty basic.
There are many things that are un- or badly documented. What is documented is documented mostly by examples that often aren't explained, leaving you unable to apply these to similar but not identical situations. And if there is some sort of explanation, chances are you won't find it because the wiki is all over the place.
Don't get me wrong, awesome is great, and I love it. It is very easy to use if you stay away from rc.lua and would be very easy to configure if rc.lua was explained properly.

Similar Messages

  • [SOLVED] Awesome's Revelation Won't Work

    Hi,
    I'm new to the Awesome WM so I will start this off by saying if you know if something little, stupid that might be causing this issue don't hesitate to mention it bc I may not know.  Anyways, I am loving using Awesome and have been messing with the config to get it to my liking. 
    I saw on the Arch Wiki that you can get "Compiz-like" effects using the Revelation widget; however, when I try to add it to my rc.lua my desktop restarts but the effects don't work and my background and a couple other configs are changed.  I tried removing the key bindings and just leaving the require ("revelation") to see if the key binding was formatted incorrectly but it still had the same problems.
    Does anyone know what might be causing these problems?  I followed the steps on the Awesome wiki on Revelation.  I was wondering if it had something to do with me copying the default config files to ~/.config/awesome as mentioned in the Arch Wiki but I am assuming it doesn't since the Arch wiki also mentions using Revelation.
    Below is my rc.lua w/ the revelation widget added (this is what would not work, just copied it then removed revelation again):
    -- Standard awesome library
    require("awful")
    require("awful.autofocus")
    require("awful.rules")
    -- Theme handling library
    require("beautiful")
    -- Notification library
    require("naughty")
    -- Widget library
    require("vicious")
    -- Compiz-like Effects
    require("revelation")
    -- {{{ Error handling
    -- Check if awesome encountered an error during startup and fell back to
    -- another config (This code will only ever execute for the fallback config)
    if awesome.startup_errors then
    naughty.notify({ preset = naughty.config.presets.critical,
    title = "Oops, there were errors during startup!",
    text = awesome.startup_errors })
    end
    -- Handle runtime errors after startup
    do
    local in_error = false
    awesome.add_signal("debug::error", function (err)
    -- Make sure we don't go into an endless error loop
    if in_error then return end
    in_error = true
    naughty.notify({ preset = naughty.config.presets.critical,
    title = "Oops, an error happened!",
    text = err })
    in_error = false
    end)
    end
    -- {{{ Variable definitions
    -- Themes define colours, icons, and wallpapers
    beautiful.init("/home/boswbr25/.config/awesome/themes/zenburn/theme.lua")
    -- This is used later as the default terminal and editor to run.
    terminal = "terminal"
    editor = os.getenv("EDITOR") or "nano"
    editor_cmd = terminal .. " -e " .. editor
    -- Default modkey.
    -- Usually, Mod4 is the key with a logo between Control and Alt.
    -- If you do not like this or do not have such a key,
    -- I suggest you to remap Mod4 to another key using xmodmap or other tools.
    -- However, you can use another modifier like Mod1, but it may interact with others.
    modkey = "Mod4"
    -- Table of layouts to cover with awful.layout.inc, order matters.
    layouts =
    awful.layout.suit.floating,
    awful.layout.suit.tile,
    awful.layout.suit.tile.left,
    -- awful.layout.suit.tile.bottom,
    -- awful.layout.suit.tile.top,
    awful.layout.suit.fair,
    -- awful.layout.suit.fair.horizontal,
    -- awful.layout.suit.spiral,
    -- awful.layout.suit.spiral.dwindle,
    awful.layout.suit.max,
    -- awful.layout.suit.max.fullscreen,
    -- awful.layout.suit.magnifier
    -- {{{ Tags
    -- Define a tag table which will hold all screen tags.
    tags = {
    names = { "main", "music", "www", "email", "office", "game", "float"},
    layout = { layouts[4], layouts[5], layouts[3], layouts[2], layouts[3],
    layouts[2], layouts[1]
    for s = 1, screen.count() do
    -- Each screen has its own tag table.
    tags[s] = awful.tag(tags.names, s, tags.layout)
    end
    -- {{{ Menu
    -- Create a laucher widget and a main menu
    myawesomemenu = {
    { "manual", terminal .. " -e man awesome" },
    { "edit config", editor_cmd .. " " .. awesome.conffile },
    { "restart", awesome.restart },
    { "quit", awesome.quit }
    mymainmenu = awful.menu({ items = { { "awesome", myawesomemenu, beautiful.awesome_icon },
    { "open terminal", terminal }
    mylauncher = awful.widget.launcher({ image = image(beautiful.awesome_icon),
    menu = mymainmenu })
    -- {{{ Wibox
    -- Pacman Widget
    pacwidget = widget({type="textbox"})
    vicious.register(pacwidget, vicious.widgets.pkg, "<span color='tan'><b> UPDATES: </b></span> $1 ", 1801, "Arch" )
    -- Initialize widget
    cpuwidget = awful.widget.graph()
    -- Graph properties
    cpuwidget:set_width(50)
    cpuwidget:set_background_color("#494B4F")
    cpuwidget:set_color("#FF5656")
    cpuwidget:set_gradient_colors({ "#FF5656", "#88A175", "#AECF96" })
    -- Register widget
    vicious.register(cpuwidget, vicious.widgets.cpu, "$1")
    -- Create a textclock widget
    mytextclock = awful.widget.textclock({ align = "right" })
    -- Create a systray
    mysystray = widget({ type = "systray" })
    -- Create a wibox for each screen and add it
    mywibox = {}
    mypromptbox = {}
    mylayoutbox = {}
    mytaglist = {}
    mytaglist.buttons = awful.util.table.join(
    awful.button({ }, 1, awful.tag.viewonly),
    awful.button({ modkey }, 1, awful.client.movetotag),
    awful.button({ }, 3, awful.tag.viewtoggle),
    awful.button({ modkey }, 3, awful.client.toggletag),
    awful.button({ }, 4, awful.tag.viewnext),
    awful.button({ }, 5, awful.tag.viewprev)
    mytasklist = {}
    mytasklist.buttons = awful.util.table.join(
    awful.button({ }, 1, function (c)
    if c == client.focus then
    c.minimized = true
    else
    if not c:isvisible() then
    awful.tag.viewonly(c:tags()[1])
    end
    -- This will also un-minimize
    -- the client, if needed
    client.focus = c
    c:raise()
    end
    end),
    awful.button({ }, 3, function ()
    if instance then
    instance:hide()
    instance = nil
    else
    instance = awful.menu.clients({ width=250 })
    end
    end),
    awful.button({ }, 4, function ()
    awful.client.focus.byidx(1)
    if client.focus then client.focus:raise() end
    end),
    awful.button({ }, 5, function ()
    awful.client.focus.byidx(-1)
    if client.focus then client.focus:raise() end
    end))
    for s = 1, screen.count() do
    -- Create a promptbox for each screen
    mypromptbox[s] = awful.widget.prompt({ layout = awful.widget.layout.horizontal.leftright })
    -- Create an imagebox widget which will contains an icon indicating which layout we're using.
    -- We need one layoutbox per screen.
    mylayoutbox[s] = awful.widget.layoutbox(s)
    mylayoutbox[s]:buttons(awful.util.table.join(
    awful.button({ }, 1, function () awful.layout.inc(layouts, 1) end),
    awful.button({ }, 3, function () awful.layout.inc(layouts, -1) end),
    awful.button({ }, 4, function () awful.layout.inc(layouts, 1) end),
    awful.button({ }, 5, function () awful.layout.inc(layouts, -1) end)))
    -- Create a taglist widget
    mytaglist[s] = awful.widget.taglist(s, awful.widget.taglist.label.all, mytaglist.buttons)
    -- Create a tasklist widget
    mytasklist[s] = awful.widget.tasklist(function(c)
    return awful.widget.tasklist.label.currenttags(c, s)
    end, mytasklist.buttons)
    -- Create the wibox
    mywibox[s] = awful.wibox({ position = "top", screen = s })
    -- Add widgets to the wibox - order matters
    mywibox[s].widgets = {
    mylauncher,
    mytaglist[s],
    mypromptbox[s],
    layout = awful.widget.layout.horizontal.leftright
    mylayoutbox[s],
    pacwidget,
    mytextclock,
    cpuwidget,
    s == 1 and mysystray or nil,
    mytasklist[s],
    layout = awful.widget.layout.horizontal.rightleft
    end
    -- {{{ Mouse bindings
    root.buttons(awful.util.table.join(
    awful.button({ }, 3, function () mymainmenu:toggle() end),
    awful.button({ }, 4, awful.tag.viewnext),
    awful.button({ }, 5, awful.tag.viewprev)
    -- {{{ Key bindings
    globalkeys = awful.util.table.join(
    awful.key({ modkey, }, "Left", awful.tag.viewprev ),
    awful.key({ modkey, }, "Right", awful.tag.viewnext ),
    awful.key({ modkey, }, "Escape", awful.tag.history.restore),
    awful.key({modkey}, "e", revelation)
    awful.key({ modkey, }, "j",
    function ()
    awful.client.focus.byidx( 1)
    if client.focus then client.focus:raise() end
    end),
    awful.key({ modkey, }, "k",
    function ()
    awful.client.focus.byidx(-1)
    if client.focus then client.focus:raise() end
    end),
    awful.key({ modkey, }, "w", function () mymainmenu:show({keygrabber=true}) end),
    -- Layout manipulation
    awful.key({ modkey, "Shift" }, "j", function () awful.client.swap.byidx( 1) end),
    awful.key({ modkey, "Shift" }, "k", function () awful.client.swap.byidx( -1) end),
    awful.key({ modkey, "Control" }, "j", function () awful.screen.focus_relative( 1) end),
    awful.key({ modkey, "Control" }, "k", function () awful.screen.focus_relative(-1) end),
    awful.key({ modkey, }, "u", awful.client.urgent.jumpto),
    awful.key({ modkey, }, "Tab",
    function ()
    awful.client.focus.history.previous()
    if client.focus then
    client.focus:raise()
    end
    end),
    -- Standard program
    awful.key({ modkey, }, "Return", function () awful.util.spawn(terminal) end),
    awful.key({ modkey, "Control" }, "r", awesome.restart),
    awful.key({ modkey, "Shift" }, "q", awesome.quit),
    awful.key({ modkey, }, "l", function () awful.tag.incmwfact( 0.05) end),
    awful.key({ modkey, }, "h", function () awful.tag.incmwfact(-0.05) end),
    awful.key({ modkey, "Shift" }, "h", function () awful.tag.incnmaster( 1) end),
    awful.key({ modkey, "Shift" }, "l", function () awful.tag.incnmaster(-1) end),
    awful.key({ modkey, "Control" }, "h", function () awful.tag.incncol( 1) end),
    awful.key({ modkey, "Control" }, "l", function () awful.tag.incncol(-1) end),
    awful.key({ modkey, }, "space", function () awful.layout.inc(layouts, 1) end),
    awful.key({ modkey, "Shift" }, "space", function () awful.layout.inc(layouts, -1) end),
    awful.key({ modkey, "Control" }, "n", awful.client.restore),
    -- Prompt
    awful.key({ modkey }, "r", function () mypromptbox[mouse.screen]:run() end),
    awful.key({ modkey }, "x",
    function ()
    awful.prompt.run({ prompt = "Run Lua code: " },
    mypromptbox[mouse.screen].widget,
    awful.util.eval, nil,
    awful.util.getdir("cache") .. "/history_eval")
    end)
    clientkeys = awful.util.table.join(
    awful.key({ modkey, }, "f", function (c) c.fullscreen = not c.fullscreen end),
    awful.key({ modkey, "Shift" }, "c", function (c) c:kill() end),
    awful.key({ modkey, "Control" }, "space", awful.client.floating.toggle ),
    awful.key({ modkey, "Control" }, "Return", function (c) c:swap(awful.client.getmaster()) end),
    awful.key({ modkey, }, "o", awful.client.movetoscreen ),
    awful.key({ modkey, "Shift" }, "r", function (c) c:redraw() end),
    awful.key({ modkey, }, "t", function (c) c.ontop = not c.ontop end),
    awful.key({ modkey, }, "n",
    function (c)
    -- The client currently has the input focus, so it cannot be
    -- minimized, since minimized clients can't have the focus.
    c.minimized = true
    end),
    awful.key({ modkey, }, "m",
    function (c)
    c.maximized_horizontal = not c.maximized_horizontal
    c.maximized_vertical = not c.maximized_vertical
    end)
    -- Compute the maximum number of digit we need, limited to 9
    keynumber = 0
    for s = 1, screen.count() do
    keynumber = math.min(9, math.max(#tags[s], keynumber));
    end
    -- Bind all key numbers to tags.
    -- Be careful: we use keycodes to make it works on any keyboard layout.
    -- This should map on the top row of your keyboard, usually 1 to 9.
    for i = 1, keynumber do
    globalkeys = awful.util.table.join(globalkeys,
    awful.key({ modkey }, "#" .. i + 9,
    function ()
    local screen = mouse.screen
    if tags[screen][i] then
    awful.tag.viewonly(tags[screen][i])
    end
    end),
    awful.key({ modkey, "Control" }, "#" .. i + 9,
    function ()
    local screen = mouse.screen
    if tags[screen][i] then
    awful.tag.viewtoggle(tags[screen][i])
    end
    end),
    awful.key({ modkey, "Shift" }, "#" .. i + 9,
    function ()
    if client.focus and tags[client.focus.screen][i] then
    awful.client.movetotag(tags[client.focus.screen][i])
    end
    end),
    awful.key({ modkey, "Control", "Shift" }, "#" .. i + 9,
    function ()
    if client.focus and tags[client.focus.screen][i] then
    awful.client.toggletag(tags[client.focus.screen][i])
    end
    end))
    end
    clientbuttons = awful.util.table.join(
    awful.button({ }, 1, function (c) client.focus = c; c:raise() end),
    awful.button({ modkey }, 1, awful.mouse.client.move),
    awful.button({ modkey }, 3, awful.mouse.client.resize))
    -- Set keys
    root.keys(globalkeys)
    -- {{{ Rules
    awful.rules.rules = {
    -- All clients will match this rule.
    { rule = { },
    properties = { border_width = beautiful.border_width,
    border_color = beautiful.border_normal,
    focus = true,
    keys = clientkeys,
    buttons = clientbuttons } },
    { rule = { class = "MPlayer" },
    properties = { floating = true } },
    { rule = { class = "pinentry" },
    properties = { floating = true } },
    { rule = { class = "gimp" },
    properties = { floating = true } },
    -- Set Firefox to always map on tags number 2 of screen 1.
    -- { rule = { class = "Firefox" },
    -- properties = { tag = tags[1][2] } },
    -- {{{ Signals
    -- Signal function to execute when a new client appears.
    client.add_signal("manage", function (c, startup)
    -- Add a titlebar
    -- awful.titlebar.add(c, { modkey = modkey })
    -- Enable sloppy focus
    c:add_signal("mouse::enter", function(c)
    if awful.layout.get(c.screen) ~= awful.layout.suit.magnifier
    and awful.client.focus.filter(c) then
    client.focus = c
    end
    end)
    if not startup then
    -- Set the windows at the slave,
    -- i.e. put it at the end of others instead of setting it master.
    -- awful.client.setslave(c)
    -- Put windows in a smart way, only if they does not set an initial position.
    if not c.size_hints.user_position and not c.size_hints.program_position then
    awful.placement.no_overlap(c)
    awful.placement.no_offscreen(c)
    end
    end
    end)
    client.add_signal("focus", function(c) c.border_color = beautiful.border_focus end)
    client.add_signal("unfocus", function(c) c.border_color = beautiful.border_normal end)
    I tried messing with the format of the key binding to make it match the other key bindings in the default rc.lua but nothing seemed to make a difference.
    Thanks,
    ~Boz~
    Last edited by boswbr25 (2012-05-03 05:17:23)

    I'm wondering if it is my graphics card's lack of 3D support that is causing the problems.  I have an older computer but have got this type of effect to work on a few DE's.  Although, it cannot run GNOME 3 and will always go into Fallback mode.
    The following is the output of lspci | grep VGA if anyone knows if this could be the issue:
    [boswbr25@boz ~]$ lspci | grep VGA
    01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 65x/M650/740 PCI/AGP VGA Display Adapter
    I totally forgot that this might be an issue when I asked the question.

  • Hyperlinks don't work in Preview

    I created a PDF file from a PowerPoint presentation using Mac OS X. My PDF file has hyperlinks in it that work fine when viewed in Acrobat Reader. But I'm unable to get any of the hyperlinks to work when viewing the file with the built in program "Preview" that is part of the Mac OS X operating system.
    There are plenty of PDF files on the Internet with hyperlinks that work in both Apple Preview and Acrobat Reader. But the PDF files I create using Mac OS X, don't seem to function properly in Preview.
    Any suggestions?

    I found this bit of information here ( http://www.cs.wright.edu/~jslater/mac-tex/mac-tex-intro/mactexintro.html):
    Adobe Reader (I wouldn’t)
    Adobe Acrobat (Not this either)
    Preview (Maybe better)
    Skim (Awesome, my pick)
    TEXShop - Works well as a viewer-only with extra tools
    iTEXMac - Also works well as a viewer-only with extra tools
    OzTEX (if not using PDFLaTEX)
    CMacTEX(if not using PDFLaTEX)
    MacDVIX (if not using PDFLaTEX)
    If PDFTEX is used, any PDF(R) viewer can be used, but hyperlinks don’t work in viewers using Apple’s(R) PDF code (e.g. Preview, iTEXMac, TEXShop, Skim...), so you may want to have Adobe Reader(R) or Acrobat installed to test your hyperlinks.

  • Hyperlinks Don't Work in Preview/Publish Mode - Correct in Design View

    I am having trouble with hyperlinks. I've deleted existing hyperlinks, then copied and pasted addresses back in but it is still not working. Any idea why this is happening.
    www.ronbrendle.com/reviews.html
    To the right of each album the links for amazon, itunes and cdbaby do not work. They DO work for the Bunky Moon album but I cannot discern any difference.  In Muse design view, the hyperlink addresses are correct when I select the amazon, itunes or cdbaby element.
    Also - when I copy a page URL from this site - it pastes the title tag. For example:
    www.ronbrendle.com/reviews.html becomes "Brendle is a monster bassist." JazzTimes
    Please help if you can.
    Thank you,
    Deanna

    I found this bit of information here ( http://www.cs.wright.edu/~jslater/mac-tex/mac-tex-intro/mactexintro.html):
    Adobe Reader (I wouldn’t)
    Adobe Acrobat (Not this either)
    Preview (Maybe better)
    Skim (Awesome, my pick)
    TEXShop - Works well as a viewer-only with extra tools
    iTEXMac - Also works well as a viewer-only with extra tools
    OzTEX (if not using PDFLaTEX)
    CMacTEX(if not using PDFLaTEX)
    MacDVIX (if not using PDFLaTEX)
    If PDFTEX is used, any PDF(R) viewer can be used, but hyperlinks don’t work in viewers using Apple’s(R) PDF code (e.g. Preview, iTEXMac, TEXShop, Skim...), so you may want to have Adobe Reader(R) or Acrobat installed to test your hyperlinks.

  • What ordinary tasks don't work with OS X 10.3.9 ?...

    Thank you folks !
    a.
    What kinds of users might not need to upgrade from OS X 10.3.9 yet?...
    b. What ordinary tasks don't work with OS X 10.3.9 ?...
    c. What other tasks don't work with OS X 10.3.9 ?...

    Hi everyone and hi fugnug,
    {quote:title=fugnug wrote:}
    There are many ordinary tasks that don't work with Panther. Browsing with Safari is a good instance. That seems to be a Mac thing, even though Safari 2 and 3 aren't for Panther, so the browsing experience just isn't as good. Safari 1 is fast, but it just won't run newer developer's scripts. The sad thing about Safari being a Mac thing is that it is supported on Windows Xp which is just as old as Panther.{quote}
    It is disappointing safari 2&3 isn't supported by Panther. But, ya know we gotta
    live with it. Windows XP is Microsoft. Panther users really don't need it with free/donationware like OpenOffice and NeoOffice. You can also try FileJuicer and
    purchase it for a small price, and it can come in really handy if you need to open Windows type documents and Stuffit deluxe for Mac can open some of them too.
    Safari 1 has a few substitutes that work very well and are current and supported.: like Seamonkey, iCab, Camino. Firefox is no longer updated current for Panther though.
    {quote}
    Another common thing like a dashboard isn't really supported.
    {quote}
    Yahoo widgets works for Panther and it's a really nice App. It was Konfabulator before Tiger was out.
    {quote}
    Also most freeware developers don't make their programs supported by Panther these days. A very common dismay for Panther users is to see a really great program and download it eagerly forgetting to look at the req-specs and then get the little disappearing icon on the dock. That crash should come with a fog horn sound effect, it would really be a good metaphor for that feeling you get. Not just freeware, but newer software like Adobe CS3. (Of course, if you had the money to buy CS3, you could probably sprig for Leopard{quote}
    There's plenty to keep you more than productive available on Versiontracker.com
    with lots and lots of older panther compatible versions. (Although not all of them are still in the severs. Just check the versions in the preview of the source at the bottom of your browser.
    {quote}
    Screen-shots is common task; AppleShift3(4). You can only save in PDFs, which we all know you can't upload to Photobucket. So you have to export from Preview, which is reminiscent of Print Screen and paste into Paint in Windows (a total turn off). I've heard there was a way to change it and I think I found a tutorial once about how to change the save screen format... but I think it was actually for Tiger, because it didn't work for me /fog horn{quote}
    You can export from preview to other formats easily by clicking on File/Export..
    Sure though, some things out there don't work on panther. Like free songs from Amazon require a special downloader compatible with 10.4.x and higher.
    If you want to listen to full songs for free, there's sites out there that let you type in what you want to listen to and you can stream it in from your browser.
    Some sites like nintendo and probably others require Firefox. So, yes. Time is ticking against panther.
    I'm in the serious consideration stage of upgrading to Tiger or Leopard. For some
    things on the Web we need to stay current. Honestly, now a days everyone who uses
    a computer needs to.
    But, Panther is a very fun and snappy OS for me. I'll miss it's simplicity and humbleness. It's been totally awesome for my family and me! It's had it's shortcomings, but I look forward to a bright future in upgrading.
    Cheers,
    L+

  • Motorola S9-HD audio controls don't work with 3GS?

    I'm the recent and proud owner of a 3GS and Motorola S9-HD headset. The headset easily pairs with the phone and plays music flawlessly (sounds awesome too). Only catch is that the only controls that work on the headset are the volume. The audio controls don't work at all.
    Anyone know of a work around for this or if I'm just out of luck...

    Word is the OS3.O for iPhone does not support full implementation of music controls via Bluetooth. Not a defect of your headset. As we all know, Apple has been dismal at implementing Bluetooth on its devices. However, word is that OS3.1 update for iPhone will fix this. I have both the Motorola S9-HD headset and the Motorola S805. Neither has full control with my iPhone 3GS using the current OS.

  • "Enable Swipe" don't work and Tablet Layout on a Smartphone

    Hi there,
    I have two big problems with my own site www.mhgrafikdesign.de:
    1. I have different slideshows in my tablet version of my site. I created the slideshow before one of the updates with the feature "Enable swipe" came out. However, it worked well on my Samsung Galaxy Tab 10.1n. Now I have a Microsoft Surface and it's not working anymore although "Enable Swipe" is enabled. I don't know if the Microsoft Surface has problems with the slideshow or one of the updates has "damaged" my slideshow. Please help me! Any ideas?
    2. I have a HTC 8S smartphone and if I type www.mhgrafikdesign.de my smartphone always show me the tablet version. Any idea why? P.S. Swiping there is also not possible.
    Many thanks for quick help. My website is my flagship in the web and it's a little bit embarrassing if my slideshow on the tab don't work... = /

    This is now a slideshow created with Muse: Homepage
    The slideshow uses fullscreen mode and was build with the latest version of Muse. On my Win8-Tablet, it is not working. I tested this with the IE11 in desktop- and in modern-ui-mode.
    Next to this problem, I also run into these things:
    1. Using the buttons to go forward and backward in the slideshow will select the text-arrow inside the button when touched.
    2. Clicking the forward- and backward-button behaves different. Windows Desktop -> slideshow does not roll back, so you can click forever in one direction, no feedback that you reached the end. On iOS -> slideshow will be rolled back and you get the visual feedback to start over again.
    3. Zoom into the fullscreen-slideshow will result in strange and not really controllabel behaviour. Zooming in does not allow to pan.
    But I am not talking only about the phones. It is more about windows tablets in general. So, content can be viewed in the InternetExplorer11 in desktop-mode and also in modern-UI-mode (touch does work in both modes). But it is also possible, that people use other browsers like Firefox and Chrome. I think, it would be a quite a good idea to translate the movement of the mousepointer into gestures. This javascript library shows what I think is a good aproach: Hammer.JS - Hammer.js

  • Adobe Flash & Javascript don't work even though Enabled

    Ever since what I think was either a Firefox upgrade (I don't know which one) or installation of Quicktime, my Adobe Flash Plugin is perpetually crashed and I cannot play any Flash content on any website. All that displays in place of the video is a gray screen with the sad-face Lego icon and the message: “The Adobe Flash Plugin has crashed. Please reload the page to try again.” (See attached image.) But it will not resolve when reloaded.
    No Flash videos on any sites work. HTML5 videos work on YouTube when tested, but non-HTML5 videos won't work.
    Also, my Javascript does not seem to be working since at least some displays requiring javascript don't work. Sometimes the display just doesn't work, and sometimes I get a message that javascript is disabled and must be enabled, but it is already enabled (set to “true” in about:config).
    I have spent days scouring every help forum entry I can find on troubleshooting Flash Player and Javascript. Everything on my end seems to be in order and I cannot find or fix either problem. I think it is possible the issue could have its roots in the fact that Javascript seems to not be working which may be preventing Flash Player content from working...??
    Also, Flash content does work in I.E. but not in Firefox (I do not have Chrome installed so did not test in Chrome). I have too many window tabs open in Firefox and can't switch to I.E. (nor do I like to use I.E.).
    PLEASE HELP as this is crippling for very important work deadlines I have.
    This is what else I know and have tried:
    I have a Toshiba Satellite C75D-A Laptop;
    Processor: AMD A6-5200 APU with Radeon HD Graphics; x64; 2.00 Ghz;
    RAM: 8 MB;
    OS: 64-bit system; Windows 8.1 (but some auto-check utilities detect it as 8.0 because it was upgraded.);
    Graphics Card: “Desktop Graphics” System – AMD Radeon HD 8400 (0x9830);
    Installed Graphics Driver Version: AMD 13.352.1004.1007 (Driver Date: 4/22/2014)
    My Device Manager graphics driver updater states: “driver software is up to date.”
    From the AMD website: the graphics driver auto-detect utility recommended the AMD Catalyst Driver (amd-catalyst-omega-14.12-without-dotnet45-win8.1-64bit.exe) I tried installing this driver, but it won't install. After trying to install, I got a message stating: “We are unable to find a driver for your system.” But Device Manager states I have a current driver, and my graphics card & driver seem to be working fine, so I do not believe this is part of the issue.
    I am using Latest Firefox version 35.0.1; and
    Using Latest Flash Player: 32-bit NPAPI Plug-in Version: 16.0.0.296; designated: “always activate” (Downloaded new update several times, including fresh install after uninstall; system & web address icons indicate Flash is enabled).
    I turned off hardware acceleration in FF Tools>Options>Advanced>General
    I disabled WebGL as explained here: https://support.mozilla.org/en-US/kb/upgrade-graphics-drivers-use-hardware-acceleration
    I am using Ad-Block Plus which has never affected things in the past. I have not tried starting FF in Safe Mode because I believe I will lose all open tabs and not be able to recover them (I may have over 200 open). But disabling add-ons has no effect (I disabled all except for Sessions Manager in case of a crash). (My No-Script has been disabled for at least six months.)
    I have Windows Media Player and Quicktime installed.
    Quicktime is most recent upgrade (7.7.6) so should not be a problem according to:
    “QuickTime plugin takes over Flash” at:
    http://kb.mozillazine.org/Flash#Disabling_Protected_Mode_in_Flash_11.3
    (note underscores in place of spaces in string; underscores not insertable here)
    Disabling Quicktime had no effect in the prior version of FF (ver. 35.0), but in latest FF ver. 35.0.1, Flash videos only display a plain (blank) gray screen instead of the sad-faced icon and crash message.
    (I tried to uninstall Quicktime altogether, but was not able to due to Error codes 2502 & 2503. I tried troubleshooting that as well with no luck using methods successful for other programs, including here:
    http://www.fixkb.com/2014/01/error-2503-and-2502-when-uninstalling-on-windows-8.html;
    & here:
    http://answers.microsoft.com/en-us/windows/forum/windows_8-winapps/re-internal-error-codes-2502-and-2503-for/ba5f2145-aa6e-4cc0-81a7-e4346f43b698.)
    Disabling my FF theme and using the default brought back the sad-faced icon and crash message in the place of videos on some YouTube pages, but not other YouTube pages (where video was still blank gray screen). It also enabled a still Flash image (an ad) to display on a different website page that previously had a Flash Plugin crash message. I have been using this same theme for a couple of years without previous issue. While turning it off did generate an effect on some still imagery, it didn't fix the video problem.
    I tried Disabling Protected Mode in Flash 11.3 as explained here:
    http://kb.mozillazine.org/Flash#Disabling_Protected_Mode_in_Flash_11.3
    (note underscores in place of spaces in string; underscores not insertable here).
    It did not solve the issue.
    I also deleted all storage & data in Flash Player as advised. This had no effect either.
    I've tried all solutions I've been able to find and am at a loss for what to try next. Please help and advise ASAP. Thank you!!

    ''guigs2 [[#answer-684038|said]]''
    <blockquote>
    I truely admire the efforts that have been made to make this work.
    "“We are unable to find a driver for your system.” "
    For it not installing, you need to follow these instructions to install them: see the comments: [http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_devices/windows-10-atiamd-display-drivers/50944d10-dde3-4e08-8244-d54eb2b1e7de] --> take warning though it looks like it has caused issues for others as well.
    Since it was working for some youtube videos and not others, there might be an issue with a particular video codec. DO you have OpenH264 Video Codec provided by Cisco Systems, Inc. plugin?
    Is it possible to try Safe Mode after saving your session with [https://addons.mozilla.org/en-US/firefox/addon/session-manager/ Session Manager Addon]? IT would test hardware acceleration in Firefox.
    </blockquote>
    Thank you, guigs2! Sorry for my delayed reply...I didn't realize I hadn't gotten back to you. Update is that I did try a whole slew of other troubleshooting steps including starting FF in safe mode, to no avail. However, I was FINALLY (after months) able to solve this problem just today by pure chance!
    The problem was that hardware acceleration was enabled in the Flash settings. I had not been able to turn it off because I didn't have access to the Flash Player settings as long as the crash error message was visible, which was all the time! Today, by a sheer fluke, I saw a static picture in place of the crash message on a Flash video. I snagged the opportunity to call up the settings and turn off hardware acceleration, and it fixed the problem for my whole browser! This has been a frustrating issue because I did not have access to the settings utility as long as I had the crash message, which was always, so my Flash was crippled without the ability for me to fix it until pure luck gave me this window of opportunity.
    Does anyone know another way to access the settings utility if this ever happens again in the future? I could not find a way. (Incidentally, I had tried disabling hardware acceleration via my graphics driver settings, but it didn't fix the problem.) We need Adobe to allow some other way to access the Flash Player settings utility when this problem arises since they aren't accessible when there is a static crash message.
    Thanks again!

  • IPod Touch: apps (facebook, twitter, facetime) don't work properly with my wireless internet having worked perfectly before. Help needed!

    I got my iPod Touch 4g for Christmas 2011 and for the first 2 weeks everything worked fine - I could download apps; use apps to their full potential; use FaceTime; use everything.
    But after the two weeks, the iPod decided to no longer work as well as it had promised. First of all, it would take more than 2 hours to download a single app from the app store and then, straight after that, I couldn't connect to FaceTime (it had worked perfectly before). Then, finally, to top it all off - Facebook and Twitter stopped working on occasions. For example, I couldn't post/send messages or photos on Twitter and at the majority of the time, the News Feeds wouldn't load.
    Sometimes everything works but most of the time it doesn't. I've tried my iPod at every time of the day and it makes no difference - nothing still works! Also, I don't think it is the fault of my wireless internet because I've had an iPod touch before and it worked perfectly, and the laptop that I am writing this question on also works perfectly with wifi.
    The weird thing is that I have used my iPod to its full potential (everything worked fine) at my friends hosue on multiple occasions - using his wifi. I am really lost for ideas for what to do - I have uninstalled all the apps that don't work with the internet (facebook, twitter) and have always made sure that I have closed apps after using them, so that my iPod wouldn't run slow.
    My iPod has been like this for over a month now, help would be appreciated

    Do you have a blackberry data plan active. On your account? You need an active blackberry data plan to use the majority of data functions on your phone, even if you are connected to wifi 

  • TV don't work with OSX Server software?

    Everything worked great BEFORE I updated our MacMini Intel to OSX Server software, now iTunes can't find the recent found Apple TV. And therefore the connection is gone and the syncing don't work anymore.
    Any work-around or suggestions on how to solve this?
    Or do I have to revert to previus userversion of OSX to make it work again?
    Is there a limitation built into OSX Server software or is there maybe some kind of firewall / preferences etc that needs to be adjusted? (The built in firewall has been disconnected.)
    FYI:
    All apps are up to date. The Mac Mini + Apple TV is on my local network at home and I'm trying to make it my family's digital hub for all family-related media.
    MacBook Pro CD2 & X-servers Mac OS X (10.4.9)
    MacBook Pro CD2 & X-servers   Mac OS X (10.4.9)  

    1) I've not tried to reset ATV from scratch. But it works fine on other Mac's on the network (sharing).
    2) Security options, yes I belive so to. I've followed all instructions and opened all ports I've seen mentioned i apples Knowledge database / support. Still don't work. Maybe I've missed some ports...
    3) YES! It works fine sharing the MacMinis lib over the network.
    4) Today I also tried to reinstall iTunes. But no luck.
    Any mor suggestions anyone? Thx
    I really wanny solve this, otherwhise my ATV is pretty useless for me...

  • Help needed! Just want to cancel my year subscription. No answer from support via mail, noone answers when I call, support chat don't work.

    Help needed! Just want to cancel my year subscription. No answer from support via mail, noone answers when I call, support chat don't work.

    Hi there
    I'll pass your details to our Russian team and they'll contact you to assist further.
    Kind regards
    Bev

  • Bookmarks exist but don't work in PDF (exported from InDesign)

    Hi all,
    I had a similar problem a few months ago where SOME cross-references within a document weren't taking you to the right place when exported to PDF although they appeared to work fine in InDesign (the "source" and "destination" arrows took you to the right place). Someone suggested exporting the file to IDML and importing again, which worked fine.
    Now I'm working on the same document (an update) but it's grown a bit and so each chapter is in its own file within a book. Problem is similar but not the same. Some cross-references work fine in the generated PDF, others are recognised as being links (cursor changes) but NO effect when clicking on them... not taking me to the wrong place, nothing is happening at all. ALSO the table of contents AND the bookmarks don't work.
    I've exported each chapter to IDML, recreated the InDesign files and recreated the book, but still no joy. If all else fails, I'll put the book back into a single file but I'd rather not go through this pain each time I have to update the book (especially as this latest change was really tiny).
    Any suggestions? Are cross-references between files in a book known to be problematic? And if they are, has the problem been addressed for CS5.5? (I'm looking to use InDesign for a journal that will contain a lot of links between elements, but the turnaround time is tight and I'm wary of this issue being a problem each month.)
    Currently using CS5 on Windows 7 Professional, and Acrobat 9 Pro Extended was installed as part of the Tech Comm Suite.
    Thanks in advance,
    Alison

    This is so funny...I was just about to close my email and look up the
    Forums to profusely thank the person who posted the solution to a similar
    problem I was having in CS4.  I'd created numerous hyperlinks in Indesign
    documents and sometimes the links worked in a pdf, and sometimes not.  The
    problem solver was talking about a solution in Word, but I found the same
    type of text in the PDF settings box that pops up when you want to save the
    pdf.  There are all kinds of checkboxes and I'd thought I was doing enough
    by checking 'add hyperlinks'...but the advisor said you have to make sure
    'tagged PDF' is CLEAR.   So the same thing will probably work for you with
    your bookmarks!  (...if the settings are similar in CS5 of course, and
    there's no reason they shouldn't be.  I guess.)
    The only thing is, there's a lot of what we call 'ant work' ahead of me.  I
    have to go back to each InDesign doc and retype the text in the home font,
    and create the hyperlinks over again.  Luckily, the hyperlink destinations
    are still there.  It's not enough just to export the document again with
    the Tagged checkbox cleared, and you can't create a new hyperlink over an
    old one; the 'new hyperlink' option isn't available under Interactive. So
    you may have the same problem.
    Let me know if this works!  I'm off to thank the person...
    Susan

  • Some share buttons don't work on my tablet

    I have a Samsung tablet, model GT-P3113 and its Operating System is Android. In some websites when I click share buttons like addthis and sharethis, they don't work and are inactive. I refresh the page and it doesn't help. For example, none of share buttons of http://www.threehosts.com/ratings/comparison-software/wordpress-vs-joomla-vs-drupal.html work on my tablet, but when I go to this page via my Laptop the share buttons work. My laptop OS is Windows 8.
    One of my friends has iPad and I sent this link to him. The share buttons work correctly for her.
    Does my problem come from my Android which doesn't support share plugins perfectly, or it comes from my tablet model?
    Is there anyone with Samsung GT-P3113 on this forum? If so, could you please test the mentioned page and tell if its share buttons are active or not?

    I have the Samsung Galaxy Tab 2,  7", model GT-P3113, wifi only (not on my Verizon plan).  It's currently running Android 4.2.2; the share buttons on the site you listed above seem to work for me...I didn't actually go through and "share" anything, but I did get to this screen and it appears that all I need to do is log in to whatever service I want to  use to share the post :

  • Upgraded to yosemite now my speakers don't work and i can't play videos on Facebook.

    When i play a video on face book I'm told i need to upgrade flashplayer, i wasn't even aware i had it downloaded! I have got rid of flash player (i think ) and now I'm told i need to download FP before i can watch videos. I can't play games on FB either and my speakers don't work.
    I wish i hadn't upgraded to Yosemite to be honest as i prefer the old layout and it seems to have caused me problems. Everything was working fine before the Upgrade to Yosemite.
    Im not good with computer terminology so please reply as simply as possible :-)
    Thank you

    Try un-installing and then re-installing.
    Adobe Flash Uninstaller
    Adobe Flash Player
    Adobe Flash Player updates available for OS X on October 24, 2014
    Sound.
    Sound – can’t hear sound from speaker - Yosemite
    Sound – No Sound After Upgrade (2)
    Sound Levels - Troubleshoot
    Sound – Troubleshooting Internal Speakers

  • Menus on some web sites don't work

    I have just activated 2 new Lumia 520 phones with Windows 8 mobile. (updated to Amber)
    When browsing the web, the menus don't work on a couple of web sites that I have written.
    These menus use Javascript to show drop down lists and to navigate to the appropriate pages. When you click a link on the menu, the drop down menu appears for a couple of seconds, then disappears. Even in the couple of seconds that the dropdown appears, it can not be clicked.
    Interestingly, these web sites also use javascript to open overlay pages when a thumbnail picture is clicked, This action works.
    These menus have been regression tested in all the major browsers and they work on a PC, Mac, iPad and Android but seem to fail on Windows 8 mobile.
    I searched and can't see any option that allows me to enable or disable Javascript.
    Here are links to those 2 sites:
    http://www.garynancy.com/index.html
    http://www.chisholmtv.com/
    What am I missing?

    The menuscript (popupmo.js) you are using will not work.
    I'd suggest you take this to http://developer.nokia.com where you will likely find more help as this is a general user to user support platform.
    Click on the blue Star Icon below if my advice has helped you or press the 'Accept As Solution' link if I solved your problem..

Maybe you are looking for