Swapping the vertex functions to a right-click menu would promote
drill-down consistency across components.
On Mon, Oct 24, 2016 at 12:26 PM, Andy LoPresto
wrote:
> I’ll throw in that while I’ve never tried to double click anything other
> than a process group in the UI (so Lee’s information was
Sir,
It worked !
Thank you very much for help.
--
View this message in context:
http://apache-nifi-developer-list.39713.n7.nabble.com/Nifi-1-0-0-HTTPS-tp13683p13708.html
Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
I’ll throw in that while I’ve never tried to double click anything other than a
process group in the UI (so Lee’s information was welcome), Matt Burgess’
explanation of “drill down” is extremely intuitive to me and is exactly how my
brain would reconcile the difference between double clicking a
I'm sort of a new user, but I surely second Matt's expressed view. It's
how I conceptualize it too.
(My two cents.)
Russ
On 10/24/2016 09:03 AM, Rob Moran wrote:
I think the logic Matt B described would make a lot of sense to experienced
users, but it is changing behavior of the action and th
I think the logic Matt B described would make a lot of sense to experienced
users, but it is changing behavior of the action and that *could* confuse
new users.
But as Lee brought up it is already being used differently, so it very well
could be appreciated as learned behavior.
It would be nice t
Certainly not the first time this has been brought up... in fact, there's
already a JIRA for it [1]. Use of double click on the connection is a great
counter point for consistency between the components.
[1] https://issues.apache.org/jira/browse/NIFI-1580
On Mon, Oct 24, 2016 at 10:45 AM, Lee Lai
Don't forget about connection behavior.
Double-click on a connection places a movable vertex on the connection.
Double-click on a vertex deletes it.
Very intuitive once you realize it's there.
Lee
> On Oct 24, 2016, at 8:21 AM, McDermott, Chris Kevin (MSDU -
> STaTS/StorefrontRemote) wr
I like this, Matt. It has often find myself double clicking to try to
configure, or view configuration. It just seems natural.
Chris McDermott
Remote Business Analytics
STaTS/StoreFront Remote
HPE Storage
Hewlett Packard Enterprise
Mobile: +1 978-697-5315
On 10/24/16, 9:50 AM, "Matt Burg
+1 for avoiding confusion or changing existing behavior, but I think a
good compromise is to leave the Configure option on both context menus
(right-click, e.g.) and add the double-click behavior to the Processor
to open the configuration dialog. In that case, the default
(double-click) option for
Yep, that's a good point and I agree we should avoid confusion with
different behaviors depending of the components.
Thanks Matt!
Pierre
2016-10-24 13:44 GMT+02:00 Matt Gilman :
> Pierre,
>
> Currently the double click action is used to enter a Process Group.
> There's been discussion in the pa
Pierre,
Currently the double click action is used to enter a Process Group. There's
been discussion in the past on this mailing about possibly using it to
configure. My only hesitation there would be the inconsistency between action
on the different components. Unless of course we also switch t
Hi,
I was wondering if there is any reason why the double click action is not
used in the UI? I think this could be a nice shortcut to access
"Configure/View configuration" view from elements on the canvas. Thoughts?
Pierre
Hi Rupert,
Could you give more details about how you have used InvokeHTTP processor?
The content of the incoming flow file will be used as content of the
request sent by InvokeHTTP processor and you can define all the parameters
in the processor. What I am not sure to understand is "the other pa
13 matches
Mail list logo
