Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dFjJg-0002WA-J8 for pgadmin-hackers@arkaria.postgresql.org; Tue, 30 May 2017 15:44:16 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dFjJg-0000t0-5i for pgadmin-hackers@arkaria.postgresql.org; Tue, 30 May 2017 15:44:16 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dFjJR-0000Tp-Rt for pgadmin-hackers@postgresql.org; Tue, 30 May 2017 15:44:02 +0000 Received: from mail-io0-x235.google.com ([2607:f8b0:4001:c06::235]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dFjJO-000485-VW for pgadmin-hackers@postgresql.org; Tue, 30 May 2017 15:44:00 +0000 Received: by mail-io0-x235.google.com with SMTP id o12so58916902iod.3 for ; Tue, 30 May 2017 08:43:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+gRtCB2MERzEmDy3MLlxIvILDDjRLYWr1I409kRoD7U=; b=KPYIynwjNXDflq0hZuH7+AeW13tA2DM0ricnzbL1P4P5Jf8lcIaq3dIkSMkMWIj9x/ 8vBTcz6QB7AKe2m9kRAPAc/vu7TUpPt4W9W+t+m81F4UMHqVpLHkgYoN3d9jBLsnyq3W a+g8lQT7UvhFVz1ATkjy8P9osvtXVCQAj08hm9r1wOdcoeRExqhlcCUAmNcua+eYuku+ A1HwaOoqznymXBuyIU5Jm2EOIaVwmJLfQ4xHt6uS+ZLFQ4ZtLkSIWgNqdQkFsPResqJP 8QhvLF2PqJwOnVkzy7YGFwrRoKpET4xf+3CkTKg2Y4u136q2Bovuy6aFBfokj0+Je1fS 5Zcw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+gRtCB2MERzEmDy3MLlxIvILDDjRLYWr1I409kRoD7U=; b=D7f7kMFezu5irrhZXBkMszjVyJU041yjP3MpqqxYMVklqRX61GAskLGwdv0qJWUepH Q6+eh0aNFUS2DIPRRSDFWH50Q4gZyuPMg8oBAjZys37zfDe7YfiGeHTrdWHjC5Hbstcv yMP0XFcWMrtLATxtWGSR0AvDmqBGX6UuV1bxTMwo2dHUVeI69cN2/EJayOtFaJskgT9d B6ezyR31uOpVBQCjt+j3KcjHvOV16BRYBbF+oSbuMtoUEjQL6a+nbBo8911LaYS+S+HQ RH74lqCf8yJTvvgGsG75WqPY7gJ4C8FmmGfElh/kJU8O3rh7KPqkyMnavo3bkvIOPYkV QRqA== X-Gm-Message-State: AODbwcCy1Hx0ij5lMksv7FZjAoUY9qCg2hnamVFjJs5lN5SjlVf29vLa tW3TnZYCqDmEBKrw2gqS7gf1BPUDCKoY7dA= X-Received: by 10.107.51.14 with SMTP id z14mr17819189ioz.84.1496159037973; Tue, 30 May 2017 08:43:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.174.147 with HTTP; Tue, 30 May 2017 08:43:57 -0700 (PDT) In-Reply-To: References: From: Dave Page Date: Tue, 30 May 2017 16:43:57 +0100 Message-ID: Subject: Re: [pgAdmin4][Patch] Add property in trigger node to display if trigger is enabled or not To: Murtuza Zabuawala Cc: pgadmin-hackers Content-Type: text/plain; charset="UTF-8" X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgadmin-hackers Precedence: bulk Sender: pgadmin-hackers-owner@postgresql.org On Mon, May 29, 2017 at 10:31 AM, Murtuza Zabuawala wrote: > Hi, > > PFA attach patch to add property into trigger node to display if trigger is > enabled or disabled in Properties panel and also in dialog. > RM#2386 The switch is added, but I cannot toggle it from the dialogue. Can you fix that please? > Also used node-list-by-name control instead of muti-select control for > listing table columns to simplify the logic. OK. Thanks! -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers