Re: [Kicad-developers] latest news on v5?

I apologize for not replying sooner but I've been really swamped at work and summer isn't the best time of the year for me to get work done. I'm still hoping to get version 5 out before the end of the summer although at this point it's looking unlikely. I'm getting close to finishing the symbol

Re: [Kicad-developers] latest news on v5?

I am still hoping to land the following features in 5.0 if the schedule allows: - GerbView GAL - Color themes I have been away from the project for the past few months due to life stuff getting in the way, but starting to get back in to it. My first priority is getting my GerbView GAL branch to

Re: [Kicad-developers] latest news on v5?

Hi Cirilo, Since no one have replied I would like to summarize very briefly. It seems that many people have been busy with other things, so the list have been at bit silent recently. The macos and windows nightlies have been down for a few weeks, but are now sort of running again. I have not

Re: [Kicad-developers] Patch: Open Datasheet in Project Dir

I see. This is also doable. I updated the patch to resolve env vars instead of relative path. Now "${KIPRJMOD}/Datasheets/tmp.pdf" will work. Thanks for the suggestion. Regards, Cheng On 31 May 2017 at 20:53, Nick Østergaard wrote: > For the 3D model paths the second example

Re: [Kicad-developers] Patch: Open Datasheet in Project Dir

For the 3D model paths the second example works, hence I would have assumed it would aslo for for other paths. Maybe that is a better solution in this case to keep things consistent. 2017-05-31 17:39 GMT+02:00 Cheng Sheng : > Hi Nick, > > Could you be a little more specific?

Re: [Kicad-developers] Patch: Open Datasheet in Project Dir

Hi Nick, Could you be a little more specific? Do you mean: - "KIPRJMOD/Datasheets/tmp.pdf"? or - "${KIPRJMOD}/Datasheets/tmp.pdf", or - "/path/to/my/project/dir/Datasheets/tmp.pdf" when KIPRJMOD=/path/to/my/project/dir? The first two doesn't work because the strings are passed to

Re: [Kicad-developers] Patch: Open Datasheet in Project Dir

Does it not work by using the KIPRJMOD as is? 2017-05-31 15:17 GMT+02:00 Cheng Sheng : > Thanks, Fabrizio. It's good to know such info that is not mentioned in the > doc. I'm indeed quite new to contributing code here. > > Regards, > Cheng > > On 31 May 2017 at 13:06,

Re: [Kicad-developers] Patch: Open Datasheet in Project Dir

Thanks, Fabrizio. It's good to know such info that is not mentioned in the doc. I'm indeed quite new to contributing code here. Regards, Cheng On 31 May 2017 at 13:06, Fabrizio Tappero wrote: > Hi Cheng, > > Don't worry you are doing just fine. > > Whenever somebody

Re: [Kicad-developers] Something new and old

Hi Orson Any help? Regards Heikki On Tue, Apr 25, 2017 at 1:31 PM, Heikki Pulkkinen wrote: > Hi Orson > > Is it possible that I can test it too? Shall we put all those pieces > together little by little. In attach there is current algorithm with my > changes, so you can

Re: [Kicad-developers] Patch: Open Datasheet in Project Dir

Hi Cheng, Don't worry you are doing just fine. Whenever somebody submits a patch, he does exactly what you did. Normally it takes some days for the patch to get submitted because in these days several people express opinions and feedback, as in your case. If nobody is against it and if the

Re: [Kicad-developers] Patch: Open Datasheet in Project Dir

okay, thanks for the info, Sergey. Don't find any explicit rule on how to select reviewers on the how to contribute page. So cc Jean-Pierre because you did a lot of commits recently. Let me know or reassign if there's some duty partitioning. Thanks.

Re: [Kicad-developers] Patch: Open Datasheet in Project Dir

On 31.05.2017 10:57, Cheng Sheng wrote: So is there any conclusion on this patch like it will be accepted or rejected or needs some improvement? Sergey, are you a patch reviewer who can commit to the repo, or I need to add someone explicitly? Thanks. No, I'm just a user who wanted to share

Re: [Kicad-developers] Patch: Open Datasheet in Project Dir

So is there any conclusion on this patch like it will be accepted or rejected or needs some improvement? Sergey, are you a patch reviewer who can commit to the repo, or I need to add someone explicitly? Thanks. Regards, Cheng On May 29, 2017 12:33 PM, "Cheng Sheng" wrote: