Attribute "target" exists, but can not be used for this element.
Resources
Attribute "target" exists, but can not be used for this element.
Msg 15175, Level 16, State 1, Procedure sp_droplogin, Line 93
Login 'qa' is aliased or mapped to a user in one or more database(s). Drop the user or alias before dropping the login.
sp_helpuser 'qa'
I've been using ubuntu for the last 6 months, really like it! But also really missing SnagIt :(
so far I have come across these screen shot tools
but none that I came across would do scrolling screen shots; currently I only needed scrolling screen shots of web pages and I just came across a great tool for that - a firefox add-on called Abduction, it is really easy to use.
For full page screen shots (including all scrollable regions) or for cropped sections of a page. Just right click on the page and select 'Save Page as Image', if you are over an 'element' it will auto select that as the cropped area, you can then adjust the crop and save, if you want the entire page the easiest seems to be right clicking where there are no elements below the mouse and then adjust the fully selected page as needed
The saved png can then be opened in Shutter for applying arrows, boxes, etc...
This sample is just a slight modification of this post 'Handling AJAX errors and displaying friendly error messages to users'. Basically I wanted to maintain the existing rails error handling for non-ajax pages and then have good handling for errors in both development and production mode; i.e. get errors in the browser when in development mode and show a nice message when in production mode.
Modify /app/controllers/application.rb; add the rescue_from macro and the handler_exception method
Then add a global javascript method for presenting the errors; most likely in application.js
Then a sample usage, jquery making an ajax post to a rails controller action
in development mode the error message is returned in an easier to read view in the firebug console and an alert message is presented that has a truncated version of the error

in production mode just a friendly error message.

Resources
http://www.laptoprepair101.com/laptop/2007/08/30/removing-replacing-laptop-keyboard/