[lively-kernel] Disabled visual connect

[Fabian Bornhofen]

Hi Jens -

just fixed at least a part of the SVG paths issue in Chrome. However,
I did not manage to re-enable visual connections. Please feel free to
try if it works.

Best,
Fabian

On Tue, Feb 14, 2012 at 12:56 PM, Jens Lincke
<jens.lincke at hpi.uni-potsdam.de> wrote:
> I disabled only the visuals... :-)
>
> Am 14.02.2012 um 17:04 schrieb "Krahn, Robert"
> <Robert.Krahn at hpi.uni-potsdam.de>:
>
> So have you disabled the feature completely or just showing a graphical
> connector (path element) while doing a visual connect?
>
> On Feb 14, 2012, at 4:27 PM, Lincke, Jens wrote:
>
> Dear List,
>
> I disabled the visual connect in webwerkstatt by adding:
>
> Config.noVisualConnect = true
> to
> http://lively-kernel.org/repository/webwerkstatt/core/lively/localconfig.js
>
> because:
> a) Chrome 17 seems to have a problem with out Path implementation.
> b) I use the visual connections a lot during Part development and I have to
> hide the connector every time, anyway
>
> If someone likes it, or a demo or test needs it, it can be locally enabled
> by executing:
>
> Config.noVisualConnect = false
>
> Best,
> Jens
>
>
> _______________________________________________
> lively-kernel mailing list
> lively-kernel at hpi.uni-potsdam.de
> http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
>
>
>
> _______________________________________________
> lively-kernel mailing list
> lively-kernel at hpi.uni-potsdam.de
> http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
>