Show messages: All
1-2
3-8
From: Michael Gibson
Hi Pior, example vid here:
- Michael
From: pior (PIOR_O)
Oh I see ! I wasn't aware of these two modes triggered by this "secret" click. I actually don't think I ever noticed the center mark either, because it is hidden most of the time except when hovering over the corners (essentially putting it in a blind spot that the gaze is never focused on). Thank you for the explanatory video.
Why not simply put a button in the UI for this mode switch, next to Add/Remove/Align/Hide ? This would make it easily discoverable.
The question of how to snap to the corners of an already placed image object remains though. Is there any know workaround for that ?
From: Michael Gibson
Hi pior,
re:
> Why not simply put a button in the UI for this mode switch, next to Add/Remove/Align/Hide ?
> This would make it easily discoverable.
It's because the same behavior exists for the edit frame being used to modify regular geometry. It's not specific to just image editing.
> The question of how to snap to the corners of an already placed image object remains though. Is there any know workaround for that ?
When you are in the image command, points for added or edited images will already snap to other image corners.
If you want to snap geometry to image corners outside of the Image command I'd recommend placing a rectangle down before placing the image.
- Michael
From: pior (PIOR_O)
Understood - well, if anything I would say that having the option for images to trigger object snapping would be great in a future release :)
On a somewhat related note : Is there a way to tell the application to always embed images, as opposed to the way it always reverts to linking to them by default ? I must say I am often surprised to see this option being turned off because of the memory of "I swear I set is as embedded last time" (as it is easy to forget that the option is applied on a per-image basis, and not as a global setting).
I do feel like having the images be embedded by default would be the safer option anyways - because it has less potential for bad surprises/work loss for the user. Or at the very least not putting this setting behind the "Properties" button, and having it in plain sight instead.
I hope this makes sense !
From: Michael Gibson
Hi pior, image embedding is not on by default because it duplicates data and increases file size.
I'll see about putting in an option to make it be turned on by default though.
- Michael
From: pior (PIOR_O)
Hello !
I think there are multiple solutions really, the point being that imho the priority should be put on error prevention - in this case making sure that the default behavior doesn't cause any loss of work. I would say there are two ways to do that (hence 4 permutations total) :
- Making the tickbox unmistakably visible when interacting with the image tool (regardless of its default setting) ;
- Setting the default behavior to embeded, as the argument could be made that file size (especially for just a small set of images) is of much less importance than making sure that the user doesn't lose work when moving files around on or sending a file over the network. I can certainly confirm that I have already lost some image planes that way in the recent past ...
Of course an .ini setting that advanced users could enable could be an acceptable solution ... but with the cavehat of potentially losing a few images first, until the user starts searching for a workaround.
Anyways ! Thanks a lot for the assistance as always. I am obviously influenced by the Blender UX here, in which the settings is set once and for all and never needs to be touched again (it even keeps the initial link to the image, meaning that it is even possible to refresh the embedded pictures as long as they are still present on disc). A great solution really.
Show messages: All
1-2
3-8
