Thanks Wayne. I will look in to wxConfig paths and see if I can see any
compelling disadvantages to bring up vs. JSON (note that JSON could be
handled by Boost.PropertyTree so no additional dependency). If I can see a
clear way to achieve the things I want to propose using wxConfig, I'm fine
On 12/1/2016 11:44 AM, Jon Evans wrote:
> Hi all,
>
> Per my recent email, I'm going to be looking in to various UI/UX things,
> starting with Eeschema, and I thought of a topic that probably warrants
> its own thread.
>
> Some of the things I want to propose would involve giving the user more
>
Hi JP,
You are correct, I'm talking about the "program configuration", not the
"project configuration" or "library configuration". I understand your
concern about adding more maintenance burden. I think there are possible
solutions that would not be significantly more complicated than wxConfig
Le 01/12/2016 à 17:44, Jon Evans a écrit :
> Hi all,
>
> Per my recent email, I'm going to be looking in to various UI/UX things,
> starting with Eeschema, and
> I thought of a topic that probably warrants its own thread.
>
> Some of the things I want to propose would involve giving the user
On 01.12.2016 17:44, Jon Evans wrote:
> Hi all,
>
> Per my recent email, I'm going to be looking in to various UI/UX things,
> starting with Eeschema, and I thought of a topic that probably warrants
> its own thread.
>
> Some of the things I want to propose would involve giving the user more
>
Hi all,
Per my recent email, I'm going to be looking in to various UI/UX things,
starting with Eeschema, and I thought of a topic that probably warrants its
own thread.
Some of the things I want to propose would involve giving the user more
options for customization of the tool (i.e. more
6 matches
Mail list logo
