Re: [Gimp-user] xcf file corrupt?
Hi, On Tue, Sep 18, 2012 at 2:35 PM, Maarten De Munck mdemu...@gmail.com wrote: Jernej Simončič schreef op ma 17-09-2012 om 20:53 [+0200]: This is the problem - if the machine crashed while the file was being written, it's possible that only a small amount of data reached the disk. Since the metadata (file name, size etc.) is updated by the OS independently, the file still looks like it has the old size, but in reality, most of that space is empty or garbage. It would be nice if Gimp (as e.g. Cinepaint does) saves the file to filename.tmp and moves that file to filename if finished correctly. That way, an error during the save process doesn't corrupt the original file. I agree. This is a must-have feature in any high grade software. Would be cool to add this feature to Gimp. Jehan ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] script-fu: illegal function?
On 09/17/12 21:44, Richard Gitschlag wrote: That's right - parentheses are not free in Scheme scripting, every opening parenthesis must be immediately followed by a function call. When you just want parentheses to group a few statements together with, call the (begin ... ) function: (begin (function a) (function b) (etc ) ... ) Thanks, both of you for clarifications. Not sure where I saw the print but it seems to work: (define (find-dot txt txtLen offset) (print foo) xyz pqr) (find-dot abcd.ef 7 1) find-dotfoo pqr (define (find-dot txt txtLen offset) (display foo) xyz pqr) (find-dot abcd.ef 7 1) find-dotfoopqr The function itself seems to be accepted. It appears the difference between using display and using print is that print outputs enclosing double quotes plus trailing newline; display outputs the unadorned string and no trailing newline. -- Stratadrake strata_ran...@hotmail.com Numbers may not lie, but neither do they tell the whole truth. Date: Mon, 17 Sep 2012 18:47:38 -0400 From: ke...@ve3syb.ca To: gimp-user-list@gnome.org Subject: Re: [Gimp-user] script-fu: illegal function? On 12-09-17 02:28 PM, Gary Aitken wrote: ((define (find-dot txt txtLen offset) (print foo)) (find-dot abcd.ef 7 1)) First, you wrapped the whole thing in ( ). Drop the leading and trailing parentheses. Second, that is a line of Scheme code and Scheme does not contain a print function. You probably meant to use display. Also keep in mind that the display function only takes a string so you may first need to convert what you pass it to a string. -- Cheers! Kevin. http://www.ve3syb.ca/ |Nerds make the shiny things that distract Owner of Elecraft K2 #2172 | the mouth-breathers, and that's why we're | powerful! #include disclaimer/favourite | --Chris Hardwick ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
[Gimp-user] procedure overloading in scheme / script-fu
I assumed from the scheme manual that procedure-overloading (in the form of different numbers of arguments) was permitted, since, for example, there are two versions of string-number. However, I can't seem to get it to work. Anything special one needs to do to overload? If you take the following code and run it in the script-fu console, it works; but replacing all occurrances of foo2 with foo gets into an infinite loop (I guess; it never returns, in any case). Is this just a user-error mistake, or is there something different needed to overload a procedure definition? I realize the two arg definition had to appear before the one arg definition which used it; if the order is wrong I get the wrong # args error, which makes sense. (define (foo2 arg1 arg2) (string-append arg1 arg2)) (define (foo arg1) (foo2 arg1 def)) (foo abc) foo2fooabcdef Thanks, Gary ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
[Gimp-user] gimp 2.8 export, after save as keeps old files name
Hello, i have a question, when i open a new file and export it with ctrl+e, the gimp 2.8 exports the file with the current file name as expected but after i save (with save as) file with a new file name, ctrl+e exports the new file with the old file name, and i think it has to be changed, because it is an absolutely new file and it is senseless to keep the old file name for exporting the new file... Is this a bug or did developers do this feature intentionally? -- realbezo (via gimpusers.com) ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
