Re: Build configuration for activation of path effect Fillet/Chamfer

Am 14.01.19 um 09:27 schrieb Jabier Arraiza:
> Hi Johannes.
> 
> Consider convert to paths your works after fillet-chamfer. Fillet
> Chamfer is not compatible with 1.0 and is removed for this.

- Looks like it has been replaced by something with the same name and
functionality, though:

http://wiki.inkscape.org/wiki/index.php/Release_notes/1.0#Fillet.2FChamfer_LPE

So, your old F+C paths don't work with that, but the functionality is
there (If I understand this correctly).

Maren

> Regards, Jabier.
> 
> 
> 
> -----Original Message-----
> From: Johannes Madel <[email protected]>
> To: [email protected]
> Subject: Re: [Inkscape-devel] Build configuration for activation of 
> path effect Fillet/Chamfer
> Date: Mon, 14 Jan 2019 04:26:15 +0100
> 
> Hello Maren,
> 
> I digged into the source code in the meantime now and found the
> solution: It is the macro LEP_ENABLE_TEST_EFFECTS in the file
> src/life_effects/effect.cpp.
> 
> I had some issues with compiling the master branch, but I wil consider
> getting that handled.
> 
> Best regards,
> Johannes Madel
> 
> Am So., 13. Jan. 2019 um 17:33 Uhr schrieb Maren Hachmann
> <[email protected]>:
>> Hi Johannes,
>>
>> as far as I know, that LPE was not fully functional in that branch
>> and
>> has been deactivated intentionally.
>>
>> It is available and maintained in the master branch, and seems to
>> work.
>>
>> Maren
>>
>> Am 13.01.19 um 07:36 schrieb Johannes Madel:
>>> Hi there,
>>>
>>> I would like to compile Inkscape in a way so that I can use the
>>> Fillet/Chamfer path effect.
>>>
>>> I got Inkscape compiled under a msys2 environment under windows 10
>>> with the macro  WITH_MODULES enabled, but I still cannot find the
>>> path
>>> effect in the list in the gui interface. As a codebase I use the
>>> source code from the gitlab repo and the branch 0.92.x.
>>>
>>> Am I missing something? I furthermore have not found the given
>>> macro
>>> in the source code (only one #ifdef in inkview.cpp which seems
>>> somewhat related). I would expect some constructs like:
>>>
>>> #ifdef WITH_MODULES
>>> /* some code */
>>> #endif
>>>
>>> Is this the correct macro to define for this use case? I am not
>>> totally sure that I did the build configuration correctly.
>>>
>>> It seems that the macro definition is supposed to more or less add
>>> steps to the build configuration. Could you point me to the files
>>> where this is done.
>>>
>>> Best regards,
>>> Johannes Madel
>>>
>>>
>>> _______________________________________________
>>> Inkscape-devel mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>>>
>>
>>
>> _______________________________________________
>> Inkscape-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
> 
> _______________________________________________
> Inkscape-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
> 
> 
> 
> _______________________________________________
> Inkscape-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>