<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Dropper and Selection in Modeling</title>
    <link>https://community.graphisoft.com/t5/Modeling/Dropper-and-Selection/m-p/107211#M56497</link>
    <description>&lt;BLOCKQUOTE&gt;Barry wrote:&lt;BR /&gt;
&lt;BR /&gt;
I agree it could do with favouring what is currently selected.&lt;BR /&gt;
It kind of does so long as you don't move the mouse away after you have selected something and then move back to alt/opt click.&lt;BR /&gt;
Select something and keep the mouse still and then alt/opt click seems to work.&lt;/BLOCKQUOTE&gt;

Not working here.&lt;BR /&gt;

&lt;BLOCKQUOTE&gt;I find if you are in the arrow tool, you cann TAB through to highlight what you want (no need to select) and then alt/opt click - but again don't move your mouse away before alt/opt clicking.&lt;/BLOCKQUOTE&gt;

Again, sadly, no.&lt;BR /&gt;

&lt;BLOCKQUOTE&gt;If you are in a tool then you must SHIFT/TAB (Windows - not sure about Macs) to highlight what you want before alt/opt clicking. And remember - don't move the mouse otherwise the selection priority resets.&lt;/BLOCKQUOTE&gt;

You'd never be in a tool to scroll through a stack. As you describe, it's extra work where a series of simple clicks with the arrow tool will reliably turn up the target eventually.&lt;BR /&gt;
&lt;BR /&gt;
Anyway, I turned pre-selection off in 10 beta 1 and never went back. IMO it's about AC trying to look busy. It's no improvement on arrow tool+watch the Info Box. Selection itself isn't a real problem though it can be tedious. It's something of a peeve of mine that they invest in such busy-lookingness while truly fundamental interactions, such as my problem, are carelessly maintained.&lt;BR /&gt;
&lt;BR /&gt;
Thanks for the tips,</description>
    <pubDate>Thu, 26 Jul 2007 11:29:17 GMT</pubDate>
    <dc:creator>James Murray</dc:creator>
    <dc:date>2007-07-26T11:29:17Z</dc:date>
    <item>
      <title>Dropper and Selection</title>
      <link>https://community.graphisoft.com/t5/Modeling/Dropper-and-Selection/m-p/107209#M56495</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;The dropper (alt/opt click) needs to favor the selected element, without exception. With a selection active at the dropper point, the dropper must ignore the active tool and the element creation order.&lt;BR /&gt;
&lt;BR /&gt;
Selection is the only way for the user to single out an element from a coincident stack. The dropper has to respect this action.&lt;BR /&gt;
&lt;BR /&gt;
In today's example, I have two slabs whose edges coincide. I can select the proper one, but the dropper unfailingly picks up the other one because it's older.&lt;BR /&gt;
&lt;BR /&gt;
The cleaner and more complete the model, the more frustration from this bug.&lt;BR /&gt;
&lt;BR /&gt;
In earlier versions this behavior was reliable; recently it has been all over the place.&lt;BR /&gt;
&lt;BR /&gt;
Without an element selected, the priority considerations are: Active tool elements beat other tool elements, and nodes beat edges. I suppose you need creation order as a tiebreaker, but this criterion means very little to the user in most cases.&lt;BR /&gt;
&lt;BR /&gt;
This was brought up in early 10 as I recall. Here it is again.&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 25 May 2023 16:32:02 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Dropper-and-Selection/m-p/107209#M56495</guid>
      <dc:creator>James Murray</dc:creator>
      <dc:date>2023-05-25T16:32:02Z</dc:date>
    </item>
    <item>
      <title>Re: Dropper and Selection</title>
      <link>https://community.graphisoft.com/t5/Modeling/Dropper-and-Selection/m-p/107210#M56496</link>
      <description>&lt;BLOCKQUOTE&gt;James wrote:&lt;BR /&gt;The dropper (alt/opt click) needs to favor the selected element, without exception. With a selection active at the dropper point, the dropper must ignore the active tool and the element creation order.&lt;BR /&gt;
&lt;BR /&gt;
Selection is the only way for the user to single out an element from a coincident stack. The dropper has to respect this action.&lt;BR /&gt;
&lt;BR /&gt;
In today's example, I have two slabs whose edges coincide. I can select the proper one, but the dropper unfailingly picks up the other one because it's older.&lt;BR /&gt;
&lt;BR /&gt;
The cleaner and more complete the model, the more frustration from this bug.&lt;BR /&gt;
&lt;BR /&gt;
In earlier versions this behavior was reliable; recently it has been all over the place.&lt;BR /&gt;
&lt;BR /&gt;
Without an element selected, the priority considerations are: Active tool elements beat other tool elements, and nodes beat edges. I suppose you need creation order as a tiebreaker, but this criterion means very little to the user in most cases.&lt;BR /&gt;
&lt;BR /&gt;
This was brought up in early 10 as I recall. Here it is again.&lt;/BLOCKQUOTE&gt;

I agree it could do with favouring what is currently selected.&lt;BR /&gt;
It kind of does so long as you don't move the mouse away after you have selected something and then move back to alt/opt click.&lt;BR /&gt;
Select something and keep the mouse still and then alt/opt click seems to work.&lt;BR /&gt;
&lt;BR /&gt;
I find if you are in the arrow tool, you cann TAB through to highlight what you want (no need to select) and then alt/opt click - but again don't move your mouse away before alt/opt clicking.&lt;BR /&gt;
&lt;BR /&gt;
If you are in a tool then you must SHIFT/TAB (Windows - not sure about Macs) to highlight what you want before alt/opt clicking. And remember - don't move the mouse otherwise the selection priority resets.&lt;BR /&gt;
&lt;BR /&gt;
It would be very hany if you could somply ALT/TAB through to what you want but in Windows at least this is the keyboard shortcut to swap applications.&lt;BR /&gt;
&lt;BR /&gt;
Barry.</description>
      <pubDate>Thu, 26 Jul 2007 02:25:41 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Dropper-and-Selection/m-p/107210#M56496</guid>
      <dc:creator>Barry Kelly</dc:creator>
      <dc:date>2007-07-26T02:25:41Z</dc:date>
    </item>
    <item>
      <title>Re: Dropper and Selection</title>
      <link>https://community.graphisoft.com/t5/Modeling/Dropper-and-Selection/m-p/107211#M56497</link>
      <description>&lt;BLOCKQUOTE&gt;Barry wrote:&lt;BR /&gt;
&lt;BR /&gt;
I agree it could do with favouring what is currently selected.&lt;BR /&gt;
It kind of does so long as you don't move the mouse away after you have selected something and then move back to alt/opt click.&lt;BR /&gt;
Select something and keep the mouse still and then alt/opt click seems to work.&lt;/BLOCKQUOTE&gt;

Not working here.&lt;BR /&gt;

&lt;BLOCKQUOTE&gt;I find if you are in the arrow tool, you cann TAB through to highlight what you want (no need to select) and then alt/opt click - but again don't move your mouse away before alt/opt clicking.&lt;/BLOCKQUOTE&gt;

Again, sadly, no.&lt;BR /&gt;

&lt;BLOCKQUOTE&gt;If you are in a tool then you must SHIFT/TAB (Windows - not sure about Macs) to highlight what you want before alt/opt clicking. And remember - don't move the mouse otherwise the selection priority resets.&lt;/BLOCKQUOTE&gt;

You'd never be in a tool to scroll through a stack. As you describe, it's extra work where a series of simple clicks with the arrow tool will reliably turn up the target eventually.&lt;BR /&gt;
&lt;BR /&gt;
Anyway, I turned pre-selection off in 10 beta 1 and never went back. IMO it's about AC trying to look busy. It's no improvement on arrow tool+watch the Info Box. Selection itself isn't a real problem though it can be tedious. It's something of a peeve of mine that they invest in such busy-lookingness while truly fundamental interactions, such as my problem, are carelessly maintained.&lt;BR /&gt;
&lt;BR /&gt;
Thanks for the tips,</description>
      <pubDate>Thu, 26 Jul 2007 11:29:17 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Dropper-and-Selection/m-p/107211#M56497</guid>
      <dc:creator>James Murray</dc:creator>
      <dc:date>2007-07-26T11:29:17Z</dc:date>
    </item>
    <item>
      <title>Re: Dropper and Selection</title>
      <link>https://community.graphisoft.com/t5/Modeling/Dropper-and-Selection/m-p/107212#M56498</link>
      <description>I agree with James. If the item is selected, then eyedroppered, then that is what you should get for the settings. What you see is what you get.&lt;BR /&gt;
&lt;BR /&gt;
David</description>
      <pubDate>Thu, 26 Jul 2007 12:06:08 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Dropper-and-Selection/m-p/107212#M56498</guid>
      <dc:creator>David Maudlin</dc:creator>
      <dc:date>2007-07-26T12:06:08Z</dc:date>
    </item>
    <item>
      <title>Re: Dropper and Selection</title>
      <link>https://community.graphisoft.com/t5/Modeling/Dropper-and-Selection/m-p/107213#M56499</link>
      <description>And now is a case of WYSIWTF…&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="http://ars.userfriendly.org/cartoons/?id=20070726" target="_blank"&gt;ars.userfriendly.org/cartoons/?id=20070726&lt;/A&gt;</description>
      <pubDate>Thu, 26 Jul 2007 12:44:48 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Dropper-and-Selection/m-p/107213#M56499</guid>
      <dc:creator>Eduardo Rolon</dc:creator>
      <dc:date>2007-07-26T12:44:48Z</dc:date>
    </item>
    <item>
      <title>Re: Dropper and Selection</title>
      <link>https://community.graphisoft.com/t5/Modeling/Dropper-and-Selection/m-p/107214#M56500</link>
      <description>&lt;BLOCKQUOTE&gt;Barry wrote:&lt;BR /&gt;It would be very hany if you could somply ALT/TAB through to what you want but in Windows at least this is the keyboard shortcut to swap applications.&lt;/BLOCKQUOTE&gt;
unfortunately for windows it is. but this is exactly how it works on a mac: TAB invokes the 'scroll through stack of elements' function in all selection/parameter transfer situations.&lt;BR /&gt;
&lt;BR /&gt;
SHIFT+TAB - chooses an element in the stack to select.&lt;BR /&gt;
&lt;BR /&gt;
ALT+TAB (or ALT+CMD+TAB) - chooses an element to use the dropper/syringe on - (parameteriz(s)e?).&lt;BR /&gt;
&lt;BR /&gt;
of course, this does mean that you do need to have 'pre-selection highlight' turned on. but turning off the bold contours, choosing a light colour and setting the highlight timer to 100 seconds minimises the hideous busy-ness of it all.&lt;BR /&gt;
&lt;BR /&gt;
that said, i do agree james, that the priority of the elements in the stack needs to be more dynamic and contextual.&lt;BR /&gt;
&lt;BR /&gt;
~/archiben</description>
      <pubDate>Thu, 26 Jul 2007 22:29:14 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Dropper-and-Selection/m-p/107214#M56500</guid>
      <dc:creator>__archiben</dc:creator>
      <dc:date>2007-07-26T22:29:14Z</dc:date>
    </item>
    <item>
      <title>Re: Dropper and Selection</title>
      <link>https://community.graphisoft.com/t5/Modeling/Dropper-and-Selection/m-p/107215#M56501</link>
      <description>I have been trying pre-selection with the interval set to the max.&lt;BR /&gt;
&lt;BR /&gt;
OK in principle by itself. But, it seems to break conventional arrow-stack-scrolling. Can't have both. You need to 'switch' to pre-selection.&lt;BR /&gt;
&lt;BR /&gt;
So pre-selection needs to handle all the cases that regular arrow-selection does, but it can't: Try a room with a finish floor slab and a finish ceiling slab, both of which fill the room, and therefore coincide perfectly. Pre-selection will cheerfully highlight both slabs, but there's no way to tell which is which.&lt;BR /&gt;
&lt;BR /&gt;
With the arrow tool, I click and watch the IB, and I know when I have what I want. AC just needs to respect my intent when I hit the dropper.</description>
      <pubDate>Tue, 07 Aug 2007 15:25:02 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Dropper-and-Selection/m-p/107215#M56501</guid>
      <dc:creator>James Murray</dc:creator>
      <dc:date>2007-08-07T15:25:02Z</dc:date>
    </item>
    <item>
      <title>Re: Dropper and Selection</title>
      <link>https://community.graphisoft.com/t5/Modeling/Dropper-and-Selection/m-p/107216#M56502</link>
      <description>&lt;BLOCKQUOTE&gt;James wrote:&lt;BR /&gt;With the arrow tool, I click and watch the IB, and I know when I have what I want. AC just needs to respect my intent when I hit the dropper.&lt;/BLOCKQUOTE&gt;
you need to have the pop-up info tag active too . . . same deal: 100 seconds . . .&lt;BR /&gt;
&lt;BR /&gt;
ben</description>
      <pubDate>Tue, 07 Aug 2007 22:17:28 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Dropper-and-Selection/m-p/107216#M56502</guid>
      <dc:creator>__archiben</dc:creator>
      <dc:date>2007-08-07T22:17:28Z</dc:date>
    </item>
    <item>
      <title>Re: Dropper and Selection</title>
      <link>https://community.graphisoft.com/t5/Modeling/Dropper-and-Selection/m-p/107217#M56503</link>
      <description>Another victory for Arrow+Info Box: When editing a patch, the Inferior Tag says a line is on 'Layer 5'. Um, thanks?&lt;BR /&gt;
&lt;BR /&gt;
If I could see the pen number/color all would be well.</description>
      <pubDate>Fri, 17 Aug 2007 17:26:06 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Dropper-and-Selection/m-p/107217#M56503</guid>
      <dc:creator>James Murray</dc:creator>
      <dc:date>2007-08-17T17:26:06Z</dc:date>
    </item>
  </channel>
</rss>

