On Sunday 08 June 2008 03:07:15 David Gowers wrote:
* support a dynamic selection of arbitrary purely calculated axis
(random, iterator, sin, cos, sawtooth, box);
A 'Dynamic selection'? what does this mean? Just that you are free to
choose one of these?
In my vision you could choose
Hi,
On Sat, 2008-06-07 at 14:51 +0200, [EMAIL PROTECTED] wrote:
The current protection mechanism for closing images is insufficient as it
doesn't
differentiate between 'saved' and 'exported'.
Yes, that is well-known and the plan is to change that at some point.
But there is no one actively
On Sunday 08 June 2008 14:28:17 Sven Neumann wrote:
On Sat, 2008-06-07 at 14:51 +0200, [EMAIL PROTECTED] wrote:
The current protection mechanism for closing images is insufficient as it
doesn't differentiate between 'saved' and 'exported'.
Yes, that is well-known and the plan is to change
Hi Alexia,
On Sun, Jun 8, 2008 at 6:18 PM, Alexia Death [EMAIL PROTECTED] wrote:
* be able to deliver constant distance and constant rate events
You mean events at a constant distance spacing or a constant time spacing?
I mean both. The dream is that paincore would only need to worry
proposed spec:
File Open/Save/Save_as_Copy only work on .xcf - all other formats must use File
Import/Export.[1]
Add File/Import and Export to handle alien formats.
File/New and File/Import would be very similar: they both create a new image
with various attributes. New gets the the
Carl Karsten wrote:
proposed spec:
File Open/Save/Save_as_Copy only work on .xcf - all other formats must use
File
Import/Export.[1]
Add File/Import and Export to handle alien formats.
Save_as_Copy and Export are the same (the user should be able to export as
.xcf).
This approach
Sven Neumann wrote:
Hi,
On Sat, 2008-06-07 at 14:51 +0200, [EMAIL PROTECTED] wrote:
The current protection mechanism for closing images is insufficient as
it doesn't
differentiate between 'saved' and 'exported'.
Yes, that is well-known and the plan is to change that at some point.
[EMAIL PROTECTED] writes:
Additionally, the 'forced .xcf' behaviour can be quite nagging - consider
user experience for a quick Levels adjustment to a photo:
[ ... ]
Where i agree with you, is that gimp should support the typical workflow
which centers around a .xcf main document with several
