Dialog box "not enough stoage" appeared on

dialog box "not enough stoage" appeared on iPad; this iPad cannot be backed up because there is not enough iCloud storage available. You can manage your storage in settings...my choices are "close" and "settings"...neither works...help?!

Reset it by holding the power and home buttons at the same time until you see the Apple logo, then release. Then use this guide to manage and free up storage space in your account: http://support.apple.com/kb/ht4847.

Similar Messages

When I run some appli like iPhoto or either, "not enough space" appears, although my mac book pro have 168 Go available. What's wrong? Thanks

When I run some appli like iPhoto or either, "not enough space" appears, although my mac book pro has 168 Go available. What's wrong? Thanks

Please select Apple menu > About This Mac > More Info… > Storage. Post a screenshot of the window, or transcribe what it shows.

CS6 Save/Save As dialog boxes not appearing

I recently installed CS6 Master Collection (educational version, if that's relevent) and in many of the programs, I can't save. In Illustrator, Dreamweaver and After Effects, I will get the spinning wheel for a moment and then nothing happens. In Photoshop, I will get the wheel for awhile before a message pops up saying "Could not complete your request because of a program error." This happens whether I use the key command or go through the File drop down menu.
If I try to exit out of the file, I will be prompted to save or don't save, but if I click save, it will just close the window and not actually save the file.
However, I have no issues saving in Indesign or Flash. The print dialog box will also appear in the trouble programs. I also have CS5 on my computer (only ai, indd, and ps) and I can save in these programs without issue.
I am operating on a MacBook Pro version 10.7.5, 2.4 GHz Intel Core i7, 8 GB 1333 MHz DDR3.
Thanks for your help.

I recently installed CS6 Master Collection (educational version, if that's relevent) and in many of the programs, I can't save. In Illustrator, Dreamweaver and After Effects, I will get the spinning wheel for a moment and then nothing happens. In Photoshop, I will get the wheel for awhile before a message pops up saying "Could not complete your request because of a program error." This happens whether I use the key command or go through the File drop down menu.
If I try to exit out of the file, I will be prompted to save or don't save, but if I click save, it will just close the window and not actually save the file.
However, I have no issues saving in Indesign or Flash. The print dialog box will also appear in the trouble programs. I also have CS5 on my computer (only ai, indd, and ps) and I can save in these programs without issue.
I am operating on a MacBook Pro version 10.7.5, 2.4 GHz Intel Core i7, 8 GB 1333 MHz DDR3.
Thanks for your help.

Save PDF File As dialog box not appearing

I am running Acrobat 8 Pro on Windows Server 2008. I'm having a problem with the Adobe PDF printer. When I attempt to print a document to this printer, the "Save PDF File As" dialog box does not appear. The dialog box does open, but it is either hidden behind the running application or is minimized. I have to click the icon on the taskbar to bring the window to focus. This problem only occurs the first time I attempt to print after logging onto the computer. On subsequent print jobs the dialog box shows up fine.

Is there a registry setting or anything that I can set to get rid of the 'Save Scanned File As' box.
No.

Why is the 'Choose icon...' button in the Options tab of the field property dialog box not enabled?

I am using Adobe Acrobat Professional XI running on Windows 8.
This “feature” has been bugging me for some time now. I remember it happening when I used Acrobat 9 Professional (Windows XP) and it is still happening in Acrobat XI Professional. I think I figured out a situation when I can reproduce this “feature” conistently and I hope someone fixes this.
Try the following and see what happens:
1. Acrobat Professional is not open.
2. Launch Word and start editing a document (or some other authoring tool that can generete PDF document).
3. After editing the document, generate a PDF version of the document.
4. Launch Acrobat Professional and edit the PDF document generated in 3.
5. Add a button.
6. View the button's properties.
7. Change the Fill Color property in the Appearance tab to none.
8. Change the Layout in the Options tab to Icon only.
Now here is what bugs be. Shouldn’t the 'Choose Icon ...' button be enabled? It is not enabled after step 8. It is possible that 'Choose Icon ...' button is enabled for some of you. I this case, it would be nice if at least one of you who experience the same bug say so in this thread so that Adobe doesn't think I am sending them on a wild goose chase.
I can enable it by selecting a different tab and then returning to the Options tab. A similar thing happens when reverting back from 'Icon only' to 'Label only' but I am not sure how to reconstruct a scenario for this one.
Here is the dialog box for one instance when I noticed the bug.
Regards,
John

You're right, it has been that way for a long time. I've never bothered reporting it as a bug since it's simple enough to deal with, but reporting it would be a reasonable thing to do.

Modeless Dialog Box Not Displaying Contents

I have created a simple modeless dialog box. Although the dialog box and title appear, the contents (a label) do not appear. The dialog box does display correctly if the dialog box is switched to a modal box.
I got into this problem because I also cannot get labels to change after their initial display on the main frame. I've tried repaint() and Thread.sleep().
Please help me, I am a newbie to Java.
Sincerely,
John

I actually had a similar problem with a JDialog containing only a progress bar, which ended up being a problem with Swing rather than my code (the bug report has already been filed). Adding a second component to the dialog fixed the problem, counterintuitive as that seems. Try it and see if that helps... If the label is a JLabel, you might try calling revalidate() on it to get the text to update.
Ian

Photoshop CS3 Save and Save As Dialog box not working

I can't do a "save as" or "save for web" in photoshop cs3. The dialog box opens and I can't change anything but the file type pull down menu (and sometimes not even that). This problem happens sporadically.... but most of the time it doesn't work.
I have re-installed Photoshop cs3 but I still have the same problem.
Photoshop CS3 10.0.1
MacPro 2 x 3 GHz Quad-Core Intel Xeon
Memory : 4GB
Mac OS 10.5.8
Please Help

I'm seeing exactly this same problem with Photoshop CS3 after the upgrade to 10.5.8. It appears that the dialog box never gets focus for "Save for Web and Devices" -- the title bar of the dialog is grayed out, while the main "Save for Web and Devices" panel still has focus. That means there's no way to clear the dialog, since the panel is waiting for it to return, but the dialog can't get any input. None of the standard resets work for any length of time. I seem to remember similar problems in a much earlier release of Mac OS X, but I can't be sure. Quite annoying.

File Save dialog box not showing correct file name while saving file

hi
Currently, after the Submit button is hit, the File Save dialog box is displayed. If the user saves the file and then opens it then the output appears correct however if the user chooses to open the file without saving on the local machine then the correct viewer is not used to display the file. The name of the file is defaulted as qotSCopPrint.jsp and the default file viewer for jsp files is chosen to view the file. The format of the file is obviously not text (it is either pdf or rtf) so the output shows binary characters.

data : v_repid like sy-repid.
parameters : p_file like rlgrap-filename.
initialization.
v_repid = sy-repid.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
CALL FUNCTION 'F4_FILENAME'
       EXPORTING
            program_name = v_repid
            dynpro_number = syst-dynnr
            field_name    = 'P_FILE'
       IMPORTING
            file_name     = p_file.
Message was edited by:
        Chandrasekhar Jagarlamudi

Awesome3 dialog boxes and pop-ups appearing partly offscreen

Dialog boxes like when opening a specific file in evince (with C-o or file->open) are appearing floating (as they should) but with almost half of the box offscreen. Its irritating to have to move my hand to my mouse every time and move the window into full view as otherwise I use the keyboard exclusively, so I'm wondering if anyone knows how to set a default location on screen for pop-up dialog boxes like this.
Thanks for any help provided.
here is my rc.lua:
-- awesome 3 configuration file
-- Include awesome library, with lots of useful function!
require("awful")
require("tabulous")
require("beautiful")
--extra non-default library
require("wicked")
-- {{{ Variable definitions
-- This is a file path to a theme file which will defines colors.
theme_path = "/home/ojcp/.config/awesome/themes/default"
-- This is used later as the default terminal to run.
terminal = "terminal"
editor = "emacs"
browserName = "Gran Paradiso"
browser = "firefox"
pdfview = "evince"
office = "abiword"
spreadsheet = "Gnumeric"
-- 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 =
"tile",
"tileleft",
"tilebottom",
"tiletop",
"fairh",
"fairv",
"magnifier",
"max",
"spiral",
"dwindle",
"floating"
-- Table of clients that should be set floating. The index may be either
-- the application class or instance. The instance is useful when running
-- a console app in a terminal like (Music on Console)
-- xterm -name mocp -e mocp
floatapps =
-- by class
["MPlayer"] = true,
["pinentry"] = true,
["gimp"] = true,
-- by instance
["mocp"] = true
-- Applications to be moved to a pre-defined tag by class or instance.
-- Use the screen and tags indices.
apptags =
[browserName] = {screen = 1, tag = 2},
[editor] = {screen = 1, tag = 4},
[office] = {screen = 1, tag = 3},
[pdfview] = {screen = 1, tag = 3},
[spreadsheet] = {screen = 1, tag = 3}
-- Define if we want to use titlebar on all applications.
use_titlebar = false
-- {{{ Initialization
-- Initialize theme (colors).
beautiful.init(theme_path)
-- Register theme in awful.
-- This allows to not pass plenty of arguments to each function
-- to inform it about colors we want it to draw.
awful.beautiful.register(beautiful)
-- Uncomment this to activate autotabbing
-- tabulous.autotab_start()
-- {{{ Tags
-- Define tags table.
tags = {}
for s = 1, screen.count() do
-- Each screen has its own tag table.
tags[s] = {}
tagnames = {"chmu","net","doc","emacs", "misc", "float"}
-- Create 9 tags per screen.
for tagnumber = 1, 6 do
if tagnumber < 6 then
tags[s][tagnumber] = tag({ name = tagnames[tagnumber], layout = layouts[1] })
else
tags[s][tagnumber] = tag({ name = tagnames[tagnumber], layout = layouts[11] })
end
-- Add tags to screen one by one
tags[s][tagnumber].screen = s
end
-- I'm sure you want to see at least one tag.
tags[s][1].selected = true
end
-- {{{ Statusbar
-- Create a taglist widget
mytaglist = widget({ type = "taglist", name = "mytaglist" })
mytaglist:mouse_add(mouse({}, 1, function (object, tag) awful.tag.viewonly(tag) end))
mytaglist:mouse_add(mouse({ modkey }, 1, function (object, tag) awful.client.movetotag(tag) end))
mytaglist:mouse_add(mouse({}, 3, function (object, tag) tag.selected = not tag.selected end))
mytaglist:mouse_add(mouse({ modkey }, 3, function (object, tag) awful.client.toggletag(tag) end))
mytaglist:mouse_add(mouse({ }, 4, awful.tag.viewnext))
mytaglist:mouse_add(mouse({ }, 5, awful.tag.viewprev))
mytaglist.label = awful.widget.taglist.label.all
-- Create a tasklist widget
mytasklist = widget({ type = "tasklist", name = "mytasklist" })
mytasklist:mouse_add(mouse({ }, 1, function (object, c) client.focus = c; c:raise() end))
mytasklist:mouse_add(mouse({ }, 4, function () awful.client.focusbyidx(1) end))
mytasklist:mouse_add(mouse({ }, 5, function () awful.client.focusbyidx(-1) end))
mytasklist.label = awful.widget.tasklist.label.currenttags
-- Create a textbox widget
mytextbox = widget({ type = "textbox", name = "mytextbox", align = "right" })
-- Set the default text in textbox
mytextbox.text = " awesome " .. AWESOME_VERSION .. " "
mypromptbox = widget({ type = "textbox", name = "mypromptbox", align = "left" })
-- Create an iconbox widget
myiconbox = widget({ type = "textbox", name = "myiconbox", align = "left" })
myiconbox.text = "<bg image=\"/usr/share/awesome/icons/awesome16.png\" resize=\"true\"/>"
-- Create a systray
mysystray = widget({ type = "systray", name = "mysystray", align = "right" })
-- Create an iconbox widget which will contains an icon indicating which layout we're using.
-- We need one layoutbox per screen.
mylayoutbox = {}
for s = 1, screen.count() do
mylayoutbox[s] = widget({ type = "textbox", name = "mylayoutbox", align = "right" })
mylayoutbox[s]:mouse_add(mouse({ }, 1, function () awful.layout.inc(layouts, 1) end))
mylayoutbox[s]:mouse_add(mouse({ }, 3, function () awful.layout.inc(layouts, -1) end))
mylayoutbox[s]:mouse_add(mouse({ }, 4, function () awful.layout.inc(layouts, 1) end))
mylayoutbox[s]:mouse_add(mouse({ }, 5, function () awful.layout.inc(layouts, -1) end))
mylayoutbox[s].text = "<bg image=\"/usr/share/awesome/icons/layouts/tilew.png\" resize=\"true\"/>"
end
-- Create battery widget
batterytext = widget({type = "textbox", name = "batterytext", align = "right"})
batterytext.text = " bat: "
mybatterymonitor = widget({type = "progressbar", name = "batterywidget", align = "right" })
mybatterymonitor.width = 50
mybatterymonitor.height = 0.6
mybatterymonitor.border_padding = 1
mybatterymonitor.border_width = 1
mybatterymonitor.ticks_count = 20
mybatterymonitor.ticks_gap = 1
mybatterymonitor.vertical = false
mybatterymonitor:bar_properties_set('bat', {
bg = 'black',
fg = 'blue4',
fg_off = 'black',
reverse = false,
min_value = 0,
max_value = 100
-- Create membar
membartext = widget({ type = "textbox", name = "membartext", align = "right" })
membartext.text = " mem: "
membarwidget = widget({
type = 'progressbar',
name = 'membarwidget',
align = 'right'
membarwidget.width = 50
membarwidget.height = 0.6
membarwidget.border_padding = 1
membarwidget.gap = 5
membarwidget.ticks_count = 20
membarwidget.ticks_gap = 1
membarwidget:bar_properties_set('mem', {
bg = 'black',
fg = '#285577',
fg_center = '#285577',
fg_end = '#285577',
fg_off = 'black',
reverse = false,
min_value = 0,
max_value = 100
wicked.register(membarwidget, wicked.widgets.mem, '$1', 1, 'mem')
-- CPU graph
cputext = widget ({ type = "textbox", name = "cputext", align = "right"})
cputext.text = " cpu: "
cpugraphwidget = widget({
type = 'graph',
name = 'cpugraphwidget',
align = 'right'
cpugraphwidget.height = 0.85
cpugraphwidget.width = 45
cpugraphwidget.bg = 'black'
cpugraphwidget.border_width = 1
cpugraphwidget.grow = 'left'
cpugraphwidget:plot_properties_set('cpu', {
fg = '#AEC6D8',
fg_center = '#285577',
fg_end = '#285577',
vertical_gradient = false
wicked.register(cpugraphwidget, wicked.widgets.cpu, '$1', 1, 'cpu')
-- mpd display
--mpdwidget = widget({
-- type = 'textbox',
-- name = 'mpdwidget',
-- align = 'left'
--wicked.register(mpdwidget, wicked.widgets.mpd,
-- function (widget, args)
-- if args[1]:find("volume:") == nil then
-- return ' Now Playing: '..args[1]
-- else
-- return ''
-- end
-- end)
-- Create a statusbar for each screen and add it
mystatusbar = {}
for s = 1, screen.count() do
mystatusbar[s] = statusbar({ position = "top", name = "mystatusbar" .. s,
fg = beautiful.fg_normal, bg = beautiful.bg_normal })
-- Add widgets to the statusbar - order matters
mystatusbar[s]:widgets({
mytaglist,
--mytasklist,
myiconbox,
mypromptbox,
mytasklist,
--mpdwidget,
cputext,
cpugraphwidget,
membartext,
membarwidget,
batterytext,
mybatterymonitor,
mytextbox,
mylayoutbox[s],
s == 1 and mysystray or nil
mystatusbar[s].screen = s
end
--bottomStatusBar = {}
--for s = 1, screen.count() do
-- bottomStatusBar[s] = statusbar({ position = "bottom", name = "bottomStatusBar" .. s,
-- fg = beautiful.fg_normal, bg = beautiful.bg_normal })
-- -- Add widgets to the statusbar - order matters
-- bottomStatusBar[s]:widgets({
-- --mytaglist,
-- mytasklist,
-- --myiconbox,
-- --mypromptbox,
-- --testbox,
-- --mytextbox,
-- --mylayoutbox[s],
-- --s == 1 and mysystray or nil
-- bottomStatusBar[s].screen = s
--end
-- {{{ Mouse bindings
awesome.mouse_add(mouse({ }, 3, function () awful.spawn(terminal) end))
awesome.mouse_add(mouse({ }, 4, awful.tag.viewnext))
awesome.mouse_add(mouse({ }, 5, awful.tag.viewprev))
-- {{{ Key bindings
-- Bind keyboard digits
-- 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
for i = 1, keynumber do
keybinding({ modkey }, i,
function ()
local screen = mouse.screen
if tags[screen][i] then
awful.tag.viewonly(tags[screen][i])
end
end):add()
keybinding({ modkey, "Control" }, i,
function ()
local screen = mouse.screen
if tags[screen][i] then
tags[screen][i].selected = not tags[screen][i].selected
end
end):add()
keybinding({ modkey, "Shift" }, i,
function ()
local sel = client.focus
if sel then
if tags[sel.screen][i] then
awful.client.movetotag(tags[sel.screen][i])
end
end
end):add()
keybinding({ modkey, "Control", "Shift" }, i,
function ()
local sel = client.focus
if sel then
if tags[sel.screen][i] then
awful.client.toggletag(tags[sel.screen][i])
end
end
end):add()
end
keybinding({ modkey }, "Left", awful.tag.viewprev):add()
keybinding({ modkey }, "Right", awful.tag.viewnext):add()
keybinding({ modkey }, "Escape", awful.tag.history.restore):add()
-- Standard program
keybinding({ modkey }, "Return", function () awful.spawn(terminal) end):add()
keybinding({ }, "F4", function () awful.spawn(browser) end):add()
keybinding({ modkey, "Control" }, "r", awesome.restart):add()
keybinding({ modkey, "Shift" }, "q", awesome.quit):add()
-- Client manipulation
keybinding({ modkey }, "m", awful.client.maximize):add()
keybinding({ modkey, "Shift" }, "c", function () client.focus:kill() end):add()
keybinding({ modkey }, "d", function () awful.client.focusbyidx(1); client.focus:raise() end):add()
keybinding({ modkey }, "f", function () awful.client.focusbyidx(-1); client.focus:raise() end):add()
keybinding({ modkey, "Shift" }, "d", function () awful.client.swap(1) end):add()
keybinding({ modkey, "Shift" }, "f", function () awful.client.swap(-1) end):add()
keybinding({ modkey, "Control" }, "d", function () awful.screen.focus(1) end):add()
keybinding({ modkey, "Control" }, "f", function () awful.screen.focus(-1) end):add()
keybinding({ modkey, "Control" }, "space", awful.client.togglefloating):add()
keybinding({ modkey, "Control" }, "Return", function () client.focus:swap(awful.client.master()) end):add()
keybinding({ modkey }, "o", awful.client.movetoscreen):add()
keybinding({ modkey }, "Tab", awful.client.focus.history.previous):add()
keybinding({ modkey }, "u", awful.client.urgent.jumpto):add()
keybinding({ modkey, "Shift" }, "r", function () client.focus:redraw() end):add()
-- Layout manipulation
keybinding({ modkey }, "l", function () awful.tag.incmwfact(0.05) end):add()
keybinding({ modkey }, "h", function () awful.tag.incmwfact(-0.05) end):add()
keybinding({ modkey, "Shift" }, "h", function () awful.tag.incnmaster(1) end):add()
keybinding({ modkey, "Shift" }, "l", function () awful.tag.incnmaster(-1) end):add()
keybinding({ modkey, "Control" }, "h", function () awful.tag.incncol(1) end):add()
keybinding({ modkey, "Control" }, "l", function () awful.tag.incncol(-1) end):add()
keybinding({ modkey }, "space", function () awful.layout.inc(layouts, 1) end):add()
keybinding({ modkey, "Shift" }, "space", function () awful.layout.inc(layouts, -1) end):add()
-- Prompt
keybinding({ modkey }, "F1", function ()
awful.prompt.run({ prompt = "Run: " }, mypromptbox, awful.spawn, awful.completion.bash,
os.getenv("HOME") .. "/.cache/awesome/history") end):add()
keybinding({ modkey }, "F4", function ()
awful.prompt.run({ prompt = "Run Lua code: " }, mypromptbox, awful.eval, awful.prompt.bash,
os.getenv("HOME") .. "/.cache/awesome/history_eval") end):add()
keybinding({ modkey, "Ctrl" }, "i", function ()
if mypromptbox.text then
mypromptbox.text = nil
else
mypromptbox.text = nil
if client.focus.class then
mypromptbox.text = "Class: " .. client.focus.class .. " "
end
if client.focus.instance then
mypromptbox.text = mypromptbox.text .. "Instance: ".. client.focus.instance .. " "
end
if client.focus.role then
mypromptbox.text = mypromptbox.text .. "Role: ".. client.focus.role
end
end
end):add()
--- Tabulous, tab manipulation
keybinding({ modkey, "Control" }, "y", function ()
local tabbedview = tabulous.tabindex_get()
local nextclient = awful.client.next(1)
if not tabbedview then
tabbedview = tabulous.tabindex_get(nextclient)
if not tabbedview then
tabbedview = tabulous.tab_create()
tabulous.tab(tabbedview, nextclient)
else
tabulous.tab(tabbedview, client.focus)
end
else
tabulous.tab(tabbedview, nextclient)
end
end):add()
keybinding({ modkey, "Shift" }, "y", tabulous.untab):add()
keybinding({ modkey }, "y", function ()
local tabbedview = tabulous.tabindex_get()
if tabbedview then
local n = tabulous.next(tabbedview)
tabulous.display(tabbedview, n)
end
end):add()
-- Client awful tagging: this is useful to tag some clients and then do stuff like move to tag on them
keybinding({ modkey }, "t", awful.client.togglemarked):add()
keybinding({ modkey, 'Shift' }, "t", function ()
local tabbedview = tabulous.tabindex_get()
local clients = awful.client.getmarked()
if not tabbedview then
tabbedview = tabulous.tab_create(clients[1])
table.remove(clients, 1)
end
for k,c in pairs(clients) do
tabulous.tab(tabbedview, c)
end
end):add()
for i = 1, keynumber do
keybinding({ modkey, "Shift" }, "F" .. i,
function ()
local screen = mouse.screen
if tags[screen][i] then
for k, c in pairs(awful.client.getmarked()) do
awful.client.movetotag(tags[screen][i], c)
end
end
end):add()
end
-- {{{ Hooks
-- Hook function to execute when focusing a client.
function hook_focus(c)
if not awful.client.ismarked(c) then
c.border_color = beautiful.border_focus
end
end
-- Hook function to execute when unfocusing a client.
function hook_unfocus(c)
if not awful.client.ismarked(c) then
c.border_color = beautiful.border_normal
end
end
-- Hook function to execute when marking a client
function hook_marked(c)
c.border_color = beautiful.border_marked
end
-- Hook function to execute when unmarking a client
function hook_unmarked(c)
c.border_color = beautiful.border_focus
end
-- Hook function to execute when the mouse is over a client.
function hook_mouseover(c)
-- Sloppy focus, but disabled for magnifier layout
if awful.layout.get(c.screen) ~= "magnifier" then
client.focus = c
end
end
-- Hook function to execute when a new client appears.
function hook_manage(c)
-- Set floating placement to be smart!
c.floating_placement = "smart"
if use_titlebar then
-- Add a titlebar
awful.titlebar.add(c, { modkey = modkey })
end
-- Add mouse bindings
c:mouse_add(mouse({ }, 1, function (c) client.focus = c; c:raise() end))
c:mouse_add(mouse({ modkey }, 1, function (c) c:mouse_move() end))
c:mouse_add(mouse({ modkey }, 3, function (c) c:mouse_resize() end))
-- New client may not receive focus
-- if they're not focusable, so set border anyway.
c.border_width = beautiful.border_width
c.border_color = beautiful.border_normal
client.focus = c
-- Check if the application should be floating.
local cls = c.class
local inst = c.instance
if floatapps[cls] then
c.floating = floatapps[cls]
elseif floatapps[inst] then
c.floating = floatapps[inst]
end
-- Check application->screen/tag mappings.
local target
if apptags[cls] then
target = apptags[cls]
elseif apptags[inst] then
target = apptags[inst]
end
if target then
c.screen = target.screen
awful.client.movetotag(tags[target.screen][target.tag], c)
end
-- Set the windows at the slave,
-- i.e. put it at the end of others instead of setting it master.
-- awful.client.setslave(c)
-- Honor size hints
c.honorsizehints = true
end
-- Hook function to execute when arranging the screen
-- (tag switch, new client, etc)
function hook_arrange(screen)
local layout = awful.layout.get(screen)
if layout then
mylayoutbox[screen].text =
"<bg image=\"/usr/share/awesome/icons/layouts/" .. awful.layout.get(screen) .. "w.png\" resize=\"true\"/>"
else
mylayoutbox[screen].text = "No layout."
end
-- If no window has focus, give focus to the latest in history
if not client.focus then
local c = awful.client.focus.history.get(screen, 0)
if c then client.focus = c end
end
-- Uncomment if you want mouse warping
local sel = client.focus
if sel then
local c_c = sel:coords()
local m_c = mouse.coords()
if m_c.x < c_c.x or m_c.x >= c_c.x + c_c.width or
m_c.y < c_c.y or m_c.y >= c_c.y + c_c.height then
if table.maxn(m_c.buttons) == 0 then
mouse.coords({ x = c_c.x + 5, y = c_c.y + 5})
end
end
end
end
-- Hook called every second
function hook_timer ()
-- For unix time_t lovers
-- mytextbox.text = " " .. os.time() .. " time_t "
-- Otherwise use:
mytextbox.text = " " .. os.date() .. " "
end
-- Custom functions
local function get_bat()
local a = io.open("/sys/class/power_supply/BAT0/energy_full")
for line in a:lines() do
full = line
end
a:close()
local b = io.open("/sys/class/power_supply/BAT0/energy_now")
for line in b:lines() do
now = line
end
b:close()
batt=math.floor(now*100/full)
mybatterymonitor:bar_data_add("bat",batt)
end
-- Set up some hooks
awful.hooks.focus.register(hook_focus)
awful.hooks.unfocus.register(hook_unfocus)
awful.hooks.marked.register(hook_marked)
awful.hooks.unmarked.register(hook_unmarked)
awful.hooks.manage.register(hook_manage)
awful.hooks.mouseover.register(hook_mouseover)
awful.hooks.arrange.register(hook_arrange)
awful.hooks.timer.register(1, hook_timer)
awful.hooks.timer.register(5, get_bat)
--startup script

Same problem here. Also happens to me in wmii. I think if the WM puts the window in floating mode without telling it where to appear somethings will appear wrong.
For me it's the Firefox Upload selection box.
It doesn't happen in ratpoison, but you can tell the floating window is getting moved after it spawns. (ratpoison has editable rules for where to put these windows)
Last edited by Procyon (2008-11-07 22:34:40)

Standard 'X' in a modal dialog box not working

Hi,
I have created a module pool and calling screen from main screen using Call screen.... Starting... ending... statement.
It is a modal dialog box screen. As a standard a [X] appears on top right corner. But when I click it doesn't work. it does not even fire PBO. How can I make it work?

Hi,
Set next screen as 0, not the screen itself. Then you are able to close it this way.
Regards
Marcin
I was wrong, this will only close the modal box each time after the dialog step is completed. To activate this magic 'X' (allow closing the window with ALT+F4) in PBO set status (type dialog box ) and activate CANCEL and CONTINUE buttons. Now when you try closing the window either by CANCEL button or using X, sy-ucomm (ok_code of the screen) will store CANCEL function code. This way you can simply say LEAVE SCREEN . That works fine, I checked.
Regards
Marcin
Edited by: Marcin Pciak on Mar 17, 2009 11:16 PM

Dialog Box not visible

Hello All,
I've a problem in Java Swing Application
My main Window opens up a child window (dialog box).
However, when I switch from my Java Application to another application and back again - the dialog box does not appear. Instead the main window is shown on the screen.
It's only after pressing ALT+TAB on my Java Swing Application, the dialog box appears.
This is problematic b'cause the dialog box is "modal" and if it does not appear first, I cannot do anything with the main window.
Is there a way to correct this?
Thanks in advance
-- Sunil
Ps: I'm creating the Swing GUI in Windows Xp

Hello Franck,
Thanks for your suggestion!
I did find the problem by tracing it to the bug database:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5063142
It seems that if you pass the "this" instance (of JFrame) directly to JDialog, the problem occurs.
However, if you pass the object that holds the JFrame instance, like you've mentioned above, the problem goes away.
I am still not satisfied as to how this occurs.
But for now, my immediate problem is resolved.
Thanks again!
Regards,
Sunil D

Flash CS3 - Missing Fonts Alert Dialog box not showing

We seem to have lost the Alert dialog box when Flash CS3 Pro
discovers there are missing fonts in a file. We still get the
warning in the Output box but we get no Alert box to tells us
actually which fonts we need to locate. This is happening
regardless of file so it appears to be Flash issue and not a file
issue.
Anyone come across this before and anyone know how to fix?

You need to make sure that the specific camera model is supported by the version of the ACR plug-in you have installed on your machine.
The current version of ACR (Adobe Camera Raw) is ACR 4.5 and there is also ACR 4.6beta.
What version are you running and what camera generated your raw files?

BPS_WB: Please Wait Dialog Box not Displaying correctly???

When we switched our Planning Interfaces to using the New Planning Interface Design the Please Wiat Dialog Box does not display correctly.
When a Request is fired and the client is waiting for the Response all that shows is a white block in the middle of the screen with no dialog screen or other information.
It maybe associated with the following:
function bpsOpenURLSelf(doIt, url)
      if (doIt) {
        try {
            document.body.style.cursor = "wait"; // works only in IE
        } catch (ex) {} // ignore
        open(url,'_self');
      // note: function with doIt==false is used to check
      //       existence of the opener window
Or it may be associated with a CSS issue?
I am currently using IE 6.0.2900.2180.
Any thoughts would be appreciated!
Thanks, ATC

Hi Alan,
please implement SAP note 845305.
Regards
Marc
SAP NetWeaver RIG

Open/save dialog boxes not working correctly.

Environment: CS6 (PS 13.0.1) Mac OS X 10.7.5. Plenty of hardware. (Generally starting with .CR2 RAW.)
Two open/save problems
Recently (maybe since the 13.0.1 update??), I have been having problems with the open and save as dialog boxes.
First. The open file dialog always defaults to Enable: blank (i.e. no file types enabled). Each time I have to go to the bottom of the dropdown list and select "All readable documents" before I can open ANY type of file. I've searched in everyway I can think of looking for some method to have OPEN default to "all readable" but can't find anyway to do this. Anyone have a suggestion? I admit this is a nuisance more than anything, but when whipping around at deadline having to stop each time and make this change is irritating. No other program has this difficulty (including Illustrator and InDesign). PS5.5 did not exhibit this behavior on the same machine.
Second. When I save as and try to select any file format, say going from psd to tiff, the format dropdown list ALWAYS selects the format ABOVE the one I choose. Example: If I select JPEG, PS tries to save as .iff. If I pull the selection down to JPEG2000 it will then save as standard JPEG. Again just an irritant but, tiff (which I need for several other programs) is last on the list thus there is no way I can go one below it to get tiff format selected. It always comes out as png. Also note that the Format selection indicates the correct format - in the case of tiff the dialog box shows TIFF selected, but the program is apending .png. (Continuing the save as (without altering my selection) always results in the incorrect format no matter what the Format dialog says in the save as operation.) Again, no other program I work with (including several Adobe products) exhibits this behavior.
I seriously need to be able to save as tiff. Anyone with any thoughts on this?
Thanks much,
Robert

I appreciate all responses particularly from an "Official Adobe" human being!
Unfortunately, a significant amount of effort has been expended with no joy here.
I have done the following;
(1) examined every plug-in folder for duplicates - None found
(2) deleted the symlinks (aliases) Topaz created referencing their plug-ins in /Library/Application Support
(3) reinstalled the Topaz bundle - no change
(4) Spoke at length with Topaz support and have been assured that all of their plug-ins are CS6 compatible.
(5) Have had the same conversation with Nik regarding their 2 plug-ins - assured that they are compatible.
Frankly I'm stumped here. I've combed my system in everyway I can without any change in PS behavior - on Open it defaults to blank and "Save as" selects the wrong format.
Question for the experts. Would deleting PS completely and then reinstalling make a difference or am I now in uncharted territory and on my own?
Thanks for all assistance,
Robert
Still need to save as TIFF but can't seem to get there.

Save Dialog Box not Opening

I have SQL 2012 running on a Windows server 2012. I just loaded the Visual Studio Business Intelligence Studo 2012 that I downloaded from Microsoft. My problem is that when I click "Save Copy of package.dtsx
As..." , instead of getting the "Save Copy of Package dialog box" , I get the regular generic windows Save Copy of box for saving to a directory file.
Is there some sort of configuration I need to do to have Save Copy of Package dialog box popup?

Hi jd51057,
When we click “Save Copy of <package file> As” on the File menu in Project Deployment Model, we can only save the package on the disk.
Please note that the procedures in the
article is about Package Deployment Model. So if we want to open the Save Copy of Package dialog box, we should change the Model first, then refer the steps in the article.
To convert the Model from Project Deployment Model to Package Deployment Model, please right-click the project to select “Convert to Package Deployment Model” option in the Solution Explorer. If a package uses features unique to the project deployment model,
such as parameters, then the package cannot be converted. So please avoid use features unique to the project deployment model.
The following screenshot is for your reference:
If there are any other questions, please feel free to ask.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Dialog box "not enough stoage" appeared on

Similar Messages

Maybe you are looking for