<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Not sure if this is the right time or place to ask but I'll
expose my concern.</p>
<p>As far as I know, currently background images are part of the UI
Data of a blend file. Disabling the option '<i>Load UI'</i> (which
I have off by default) will cause background images to vanish on
load.<br>
Would it be feasible to change this so they somehow belong to
scene data instead and aren't lost if UI data is not loaded?</p>
<p><br>
</p>
<p>One other interesting feature request would be to introduce some
sort of non permanent '<i>per-session'</i> view history, so one
could go back to a previous scene view state.<br>
Kind of like an an undo system for scene view changes only (like
move-view or rotate-view operators and perhaps the new view
shading changes too). Or at least allow cancelling a view
transform operation during execution, like right-clicking during
move-view or rotate-view would simply revert to exactly where we
were before.</p>
<p><br>
</p>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 15-10-2016 01:15, Julian Eisel
wrote:<br>
</div>
<blockquote
cite="mid:CADUt0s8S+LSS4k2xarFh9JtW+08PNQ54gDXr64goG+tBDfVMPw@mail.gmail.com"
type="cite">
<pre wrap="">@Jacob,
Floating UI panels for VR interaction (i remember you asking about
this a couple of times) could be drawn even with current viewport,
that's not the problem. The problem is designing the interactions,
reading the pointing device input and making our event pipeline map it
correctly to the interface handling code. All of this has nothing to
do with the viewport and is it's own project.
As for the idea of a plane with a UV mapped UI on it, I've seen you
proposing this a couple of times too. To make it short: It's an overly
complicated approach for something that could be solved much easier
and less abstract. It isn't related to the viewport project either.
Cheers,
- Julian -
On 15 October 2016 at 00:48, Jacob Merrill <a class="moz-txt-link-rfc2396E" href="mailto:blueprintrandom1@gmail.com"><blueprintrandom1@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">can the user ui be drawn inside the viewport? like a overlay?
like imagine a transparent window on top of the viewport that was a plane
containing the ui, mousing over gets the uv, and translates it into a
mouseover context?
this way custom panels could be added very very easily, panels would also be
very good for VR and be future proof.
On Oct 14, 2016 3:20 PM, "Dalai Felinto" <a class="moz-txt-link-rfc2396E" href="mailto:dfelinto@gmail.com"><dfelinto@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
Hi there [*],
We haven't discussed UI (user interface) for the viewport yet. Even
during the Sprint we focused on the internal functionalities, as
opposed to how the user would access it.
There is a lot of overlap with the layer-manager work Julian Eisel
(Severian) is leading. So after some back and forth, we (Brecht,
Julian, Mike and I) seemed to have reached an agreement on the final
design (or rather, the principles behind the design) - guys correct me
if I'm wrong.
The idea is to leave which objects to show, and overrides handling
outside the viewport. This will be handled by the layer manager
project.
Options such as having the main object fully shaded with the rest of
the scene with clay render will be provided as built-in shading
options. Not configurable per "layer".
A visual draft of the UI is here [**]:
<a class="moz-txt-link-freetext" href="https://docs.google.com/drawings/d/1CDvy3ClsuIol7PjN25v04GgVbHg7uEN1VEQ9vmBPlyU/edit?usp=sharing">https://docs.google.com/drawings/d/1CDvy3ClsuIol7PjN25v04GgVbHg7uEN1VEQ9vmBPlyU/edit?usp=sharing</a>
As always, let us know any thoughts you may have on any of this.
Related messages:
* <a class="moz-txt-link-freetext" href="https://lists.blender.org/pipermail/bf-viewport/2016-October/000231.html">https://lists.blender.org/pipermail/bf-viewport/2016-October/000231.html</a>
* <a class="moz-txt-link-freetext" href="https://lists.blender.org/pipermail/bf-viewport/2016-October/000233.html">https://lists.blender.org/pipermail/bf-viewport/2016-October/000233.html</a>
For anyone interested on the thought process, this is an early design
I presented today, on top of which we discussed.
<a class="moz-txt-link-freetext" href="https://docs.google.com/drawings/d/1_z4EihqVTidAyg3DtzS84J1XZZSScF8fuQFIbzme0HA/edit?usp=sharing">https://docs.google.com/drawings/d/1_z4EihqVTidAyg3DtzS84J1XZZSScF8fuQFIbzme0HA/edit?usp=sharing</a>
[*] - (cross posting on bf-viewport and bf-interface, but let's keep
the discussion on bf-viewport please)
[**] - on google docs to gather feedback, and later to be moved to the
wiki
Best regards,
Dalai
--
blendernetwork.org/dalai-felinto
<a class="moz-txt-link-abbreviated" href="http://www.dalaifelinto.com">www.dalaifelinto.com</a>
_______________________________________________
Bf-viewport mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bf-viewport@blender.org">Bf-viewport@blender.org</a>
<a class="moz-txt-link-freetext" href="https://lists.blender.org/mailman/listinfo/bf-viewport">https://lists.blender.org/mailman/listinfo/bf-viewport</a>
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
Bf-viewport mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bf-viewport@blender.org">Bf-viewport@blender.org</a>
<a class="moz-txt-link-freetext" href="https://lists.blender.org/mailman/listinfo/bf-viewport">https://lists.blender.org/mailman/listinfo/bf-viewport</a>
</pre>
</blockquote>
<pre wrap="">_______________________________________________
Bf-viewport mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bf-viewport@blender.org">Bf-viewport@blender.org</a>
<a class="moz-txt-link-freetext" href="https://lists.blender.org/mailman/listinfo/bf-viewport">https://lists.blender.org/mailman/listinfo/bf-viewport</a>
</pre>
</blockquote>
<br>
</body>
</html>