File export folder.
This used to be the folder of the main file but then I remember it being
changed to be where an export was done last. That doesn't work for my
workflow and was very annoying.
However the current snapshot seems to have changed again. It is now where
you last opened a file via an open dialog. In MDI mode this makes no sense
at all and caused me to waste an hour slicing the same file over and over
again, wondering why it wasn't changing.
I propose making it default to the folder of the main file again. That is
the only thing that makes sense to me because all my projects look the
same, they have an stl folder which is one click away. I could make it an
option if people really object but I don't see how the current situation
works for anybody. If you use the recent file list top open it doesn't set
it at all, so it is forever in the wrong place.
I can't see any direct changes lately, maybe it's some side
effect of other changes, or the new Qt behaves differently.
Anyway, it makes sense to have some useful defaults (there
was some discussion in issue 649).
How about:
- Remember the last folder per main file + per export type
- Change to default once the main file changes (new / save-as)
2.a) unsaved main file: default to the platform document folder
2.b) saved main file: use same folder as main file
It might be useful to have a config setting for 2.a but I
think that could be a separate feature request.
ciao,
Torsten.
When you "remember" do you mean in storage such as the registry? It could
end up as a lot of data that doesn't get used again. If on the other hand
it isn't persisted it seems hardly worth it. Simply always starting where
the main file is like Save As seems more normal behaviour. The only other
program I have that behaves like this is NetFabb studio and that is a
complete pain because of it as well.
On Sat, 22 Dec 2018 at 14:22, Torsten Paul Torsten.Paul@gmx.de wrote:
I can't see any direct changes lately, maybe it's some side
effect of other changes, or the new Qt behaves differently.
Anyway, it makes sense to have some useful defaults (there
was some discussion in issue 649).
How about:
- Remember the last folder per main file + per export type
- Change to default once the main file changes (new / save-as)
2.a) unsaved main file: default to the platform document folder
2.b) saved main file: use same folder as main file
It might be useful to have a config setting for 2.a but I
think that could be a separate feature request.
ciao,
Torsten.
OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
On 22.12.18 16:05, nop head wrote:
When you "remember" do you mean in storage such as the registry?
Not permanent storage, so: remember in memory while OpenSCAD
is running. Reverting back to defaults when starting the App
again.
The only other program I have that behaves like this is
NetFabb studio and that is a complete pain because of it
as well.
Why? Also I just tried gimp (on Linux) and it behaves exactly
like that too. LibreOffice does not, it always goes to the
Documents folder (regardless of the document itself).
ciao,
Torsten.
NetFabb is annoying because when I open an STL, modify it and export the
result I always want it to be in the folder I opened it from, not where I
last exported an STL weeks ago.
OpenSCAD is annoying because all my projects have the same structure of
folders and files so it easy to export STLs in the wrong place when in MDI
mode.
LibraOffice on Win 7 seems to export where it did last time, again this is
annoying as there is no reason to think I want to export to where I did
months ago rather than in the same folder as the document.
I will have a go at implementing it defaulting to the main file's folder
and then remembering it per file type if you save it somewhere else.
On Sat, 22 Dec 2018 at 15:40, Torsten Paul Torsten.Paul@gmx.de wrote:
On 22.12.18 16:05, nop head wrote:
When you "remember" do you mean in storage such as the registry?
Not permanent storage, so: remember in memory while OpenSCAD
is running. Reverting back to defaults when starting the App
again.
The only other program I have that behaves like this is
NetFabb studio and that is a complete pain because of it
as well.
Why? Also I just tried gimp (on Linux) and it behaves exactly
like that too. LibreOffice does not, it always goes to the
Documents folder (regardless of the document itself).
ciao,
Torsten.
OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
On 23.12.18 15:50, nop head wrote:
NetFabb is annoying because when I open an STL, modify it and
export the result I always want it to be in the folder I opened
it from, not where I last exported an STL weeks ago.
Right, we certainly don't want that behavior.
I will have a go at implementing it defaulting to the main
file's folder and then remembering it per file type if you save
it somewhere else.
Awesome. As note regarding unsaved files, I'm not sure if
PlatformUtils::documentsPath() is actually the "Documents"
we would expect for this scenario. It might be slightly
misnamed.
ciao,
Torsten.
On 12/23/2018 8:59 AM, Torsten Paul wrote:
On 23.12.18 15:50, nop head wrote:
NetFabb is annoying because when I open an STL, modify it and
export the result I always want it to be in the folder I opened
it from, not where I last exported an STL weeks ago.
Right, we certainly don't want that behavior.
For a .STL to .STL edit/save-as, I agree.
For a .SCAD to .STL export... I'd like it if it wasn't even considered a
"save-as" / "export" type operation, but rather a "build" operation that
always builds to the same name as the source file, in the source
directory. (Maybe there should be a configuration override available,
for those who want to keep their source trees pristine.)
However, for the somewhat (but only somewhat) similar .STL to .GCODE
export, it's very convenient that my slicer defaults to exporting to the
same place I last exported to, because that's the USB stick that I'm
about to move over to the printer.
That would imply a configuration option for each file type that could be
relative to the main file's folder or absolute if you want them all
together. It could default to .
It works for my use case because I have stls in a folder called stls, dxf
in a folder called dxfs, etc.
If you change the folder with the export dialogue then it remembers it per
window as discussed before. How does that sound?
On Sun, 23 Dec 2018 at 21:33, Jordan Brown openscad@jordan.maileater.net
wrote:
On 12/23/2018 8:59 AM, Torsten Paul wrote:
On 23.12.18 15:50, nop head wrote:
NetFabb is annoying because when I open an STL, modify it and
export the result I always want it to be in the folder I opened
it from, not where I last exported an STL weeks ago.
Right, we certainly don't want that behavior.
For a .STL to .STL edit/save-as, I agree.
For a .SCAD to .STL export... I'd like it if it wasn't even considered a
"save-as" / "export" type operation, but rather a "build" operation that
always builds to the same name as the source file, in the source
directory. (Maybe there should be a configuration override available, for
those who want to keep their source trees pristine.)
However, for the somewhat (but only somewhat) similar .STL to .GCODE
export, it's very convenient that my slicer defaults to exporting to the
same place I last exported to, because that's the USB stick that I'm about
to move over to the printer.
OpenSCAD mailing list
Discuss@lists.openscad.org
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
Mostly, my comment was around the notion that there's a tension between
having all cases (including across programs) have the same behavior, and
wanting behaviors that "do the right thing" for particular cases. The
right thing for edit/save-as is not necessarily the same thing as for
the particular case of generate/export gcode.
On 12/23/2018 4:39 PM, nop head wrote:
That would imply a configuration option for each file type that could
be relative to the main file's folder or absolute if you want them all
together. It could default to .
It works for my use case because I have stls in a folder called stls,
dxf in a folder called dxfs, etc.
Works for me, but I don't claim to have a truly mature workflow.
If you change the folder with the export dialogue then it remembers it
per window as discussed before. How does that sound?
Doesn't sound silly, but I don't really have a workflow that would make
use of the ability to control the STL location and name (other than to
control clutter) and so I don't have much of an opinion. For my own
work, STLs are very much an intermediate format; if they were deleted
automatically after I slice them, that would be more or less OK.
As long as we're in this area, can w have options that mean "always use
the default name and location" and "overwrite existing STL without
asking"? Basically, I want it to "do the right thing" when I punch the
"STL" button, without the need to prompt me.
(Pipe dream would involve an interaction with the slicer where hitting
the "STL" button would then cause the slicer to reload the STL. But
that would require work on the slicer side.)
Along with the folder per file type could be a tick box to suppress the
dialogue. I think it would need to be a new tab in the preferences
dialogue.
On Mon, 24 Dec 2018 at 01:02, Jordan Brown openscad@jordan.maileater.net
wrote:
Mostly, my comment was around the notion that there's a tension between
having all cases (including across programs) have the same behavior, and
wanting behaviors that "do the right thing" for particular cases. The
right thing for edit/save-as is not necessarily the same thing as for the
particular case of generate/export gcode.
On 12/23/2018 4:39 PM, nop head wrote:
That would imply a configuration option for each file type that could be
relative to the main file's folder or absolute if you want them all
together. It could default to .
It works for my use case because I have stls in a folder called stls, dxf
in a folder called dxfs, etc.
Works for me, but I don't claim to have a truly mature workflow.
If you change the folder with the export dialogue then it remembers it per
window as discussed before. How does that sound?
Doesn't sound silly, but I don't really have a workflow that would make
use of the ability to control the STL location and name (other than to
control clutter) and so I don't have much of an opinion. For my own work,
STLs are very much an intermediate format; if they were deleted
automatically after I slice them, that would be more or less OK.
As long as we're in this area, can w have options that mean "always use
the default name and location" and "overwrite existing STL without
asking"? Basically, I want it to "do the right thing" when I punch the
"STL" button, without the need to prompt me.
(Pipe dream would involve an interaction with the slicer where hitting the
"STL" button would then cause the slicer to reload the STL. But that would
require work on the slicer side.)