Chris wrote:
As far as I know, you can't put PNG files directly only the clipboard, at least not in a neutral format understood by any application.
...I guess I might've quoted the wrong part of your post, I wasn't meaning to put a png on the clipboard (I don't care what format it is on the clipboard), but you mentioned bmp->disk...
Chris wrote:
(by loading them on the clipboard, pasting them into an image program, and then saving).
...
Unfortunately, converting a BMP on the clipboard into a BMP file on disk
...so I was really on the bmp->disk track & not on the bmp->clipboard track...so what I meant was, if you get bmp->disk support, can you also support png->disk?...or really that means CB->disk as bmp & CB->disk as png.
Chris wrote:
If you use a particular application that is able to copy & paste PNG images within its own windows
...no, SSA watches the clipboard for images (normally put there by pressing Print Screen) & writes them to disk using settings you gave it beforehand (what dir, what filename prefix, what format).
Chris wrote:
Since AutoHotkey is designed to be tightly integrated (not requiring any registry entries nor any DLLs), I don't think this would be worth it unless there was some huge benefit.
...can't you support a command that links into a dll, but if the person don't have the dll, that command just don't work? It won't need to require the dll (for all scripts), it can just ignore that command (or give an error) if someone tries to use it without having the dll. The only other option is to write your own image routines, which would increase the size of all scripts & perhaps not have as good of file sizes (on png's). I think certain commands using external dlls, isn't a bad thing...cuz (it don't increase every .exe's file size &) you can put in the help file "use of this command requires this dll on the target computer". I'm sure other AHKers are on track with the no-dll thing, but as long as the dll is only required *if* a script *uses* that command, I think it's ok. Poll anyone?: Should a few ahk commands be allowed to link into external dlls?...almost the same as using an external .exe (BoBo), but this image writing thing is a dll & not an exe, so I can't use it that way.
Chris wrote:
I don't see a significant benefit to forcing white
...would it be too much to ask you to compile a 2nd help file with white?...read on before you say "Yes (it would it be too much to ask)". You could (write an ahk script to), compile normally, rename "default.css" to "default-hold.css", rename "default-white.css" to "default.css", recompile & then rename both back, this way you only rename a file & recompile & don't need to re-configure the help compiler (to use one css the 1st time & another the 2nd time) (unless having 2 help projects is easier than renaming???). If not that, could you provide your .hpj? Cuz when I de-compiled it before that was the one file it didn't give me & I had to guess at until I got it configured like you have it (with the buttons & help window names).
Chris wrote:
and keeping it the way it is allows anyone to select a custom background color.
...it doesn't let me choose an AHK background color, it makes me change my browser default to accommodate one page. This don't help the compiled help file, but on the web, you can provide an "alternate style" & I can pick it in the browser, cuz the online help still looks like crap & I can't fix that. Actually, I'm not sure how persistent "alternate style"s are, if I need to re-pick the alternate style on every visit or if the browser remembers it, if you test that & it's not persistent, would you mind if I code some cookies to remember a user bgcolor (that you put on the help pages)?
Chris wrote:
For example, if you visit
http://www.yahoo.com with MSIE, your custom background color should be in effect there too. Contrary opinions are welcome.
...yes, alot of sites have not specified a background color (& look like crap), but I don't think most of them do it to "use your custom background color" I think they do it, cuz in their IE, when they test it, white is default, so they think everyone else's is white too & don't even think about setting it.
...this board specifies colors for everything...& looks good...
Why is the new variable called ClipboardAll & not ClipboardRaw (All what?)? Why do most operations have to be on a "saved" version of it & not directly on ClipboardAll?
_________________
AutoHotkey-Hotstring.ahk - Helping the world spell "AutoHotkey" correctly! (btw, it's a lowercase k!)