Thanks Nick, that made the resulting cpp files even smaller thanks to
pngcrush!
On 6/08/19 9:15 PM, Nick Østergaard wrote:
> Maybe I am off here, butnis there any reason why you can just enable
> the MAINTAIN_PNGS option to make it convert the svg to cpp?
>
> tir. 6. aug. 2019 06.01 skrev
Hi Fellow Devs,
I'm fixing some memory management issues in the P by introducing smart
pointers here and there. Do we have any coding policy on typedefing
shared_ptrs/unique_ptrs?
Should I:
- always use std::shared_ptr explicitly?
- or am I allowed to typedef std::shared_ptr TYPE_SP (or
On 07/08/2019 19:45, Jeff Young wrote:
> Hi Orson,
>
> I wanted to keep the selection highlight shadows uncached, but they need to
> go above the device backgrounds and sheet backgrounds.
>
> I can go ahead and put them in cached. (I just need to add some code to
> redraw them when the zoom
Hi Tom,
I don’t know a thing about them but it’s probably time I bone up on this whole
OpenGL thing anyway, so I’ll look into it.
Cheers,
Jeff.
> On 7 Aug 2019, at 19:17, Tomasz Wlostowski wrote:
>
> On 07/08/2019 19:45, Jeff Young wrote:
>> Hi Orson,
>>
>> I wanted to keep the selection
On 07/08/2019 19:45, Jeff Young wrote:
> Hi Orson,
>
> I wanted to keep the selection highlight shadows uncached, but they need to
> go above the device backgrounds and sheet backgrounds.
>
> I can go ahead and put them in cached. (I just need to add some code to
> redraw them when the zoom
Hi Orson,
I needed to make a current-probe, so I created a new voltage-probe to match.
Try the SPICE probe out and see what you think. (You should get a
voltage-probe over wires and a current-probe over pins.)
Cheers,
Jeff.
> On 7 Aug 2019, at 13:37, Maciej Suminski wrote:
>
> Hi Jeff,
>
Hi Orson,
I wanted to keep the selection highlight shadows uncached, but they need to go
above the device backgrounds and sheet backgrounds.
I can go ahead and put them in cached. (I just need to add some code to redraw
them when the zoom level changes.)
Cheers,
Jeff.
> On 7 Aug 2019, at
Yes. There is an issue on the 5.1.3 of kicad-doc that and we need to
include the fix for that in 5.1.4 and test it.
ons. 7. aug. 2019 17.44 skrev Wayne Stambaugh :
>
>
> On 8/7/19 9:33 AM, Steven A. Falco wrote:
> > On 8/5/19 9:35 AM, Steven A. Falco wrote:
> >> On 8/4/19 6:02 PM, Rene Pöschl
On 8/7/19 9:33 AM, Steven A. Falco wrote:
> On 8/5/19 9:35 AM, Steven A. Falco wrote:
>> On 8/4/19 6:02 PM, Rene Pöschl wrote:
>>> On 04/08/2019 19:03, Wayne Stambaugh wrote:
Please tag the doc, translation,
and library repos to 5.1.4 using the same commit as 5.1.3. I'll update
On 8/5/19 9:35 AM, Steven A. Falco wrote:
> On 8/4/19 6:02 PM, Rene Pöschl wrote:
>> On 04/08/2019 19:03, Wayne Stambaugh wrote:
>>> Please tag the doc, translation,
>>> and library repos to 5.1.4 using the same commit as 5.1.3. I'll update
>>> the release announcement and there will be no
Hi Jeff,
I am afraid I have lost them in a hard drive crash. I should have
committed them to the repository, my bad. I have an idea how to quickly
convert them back to the original version. Are you still interested in
the sources?
Cheers,
Orson
On 8/5/19 6:06 PM, Jeff Young wrote:
>
>
>
Hi Jeff,
I am afraid it is not possible. We use two framebuffers for rendering:
the cached one keeps in the video memory vertices that are not likely to
change in the near future, the non-cached is for vertices that are
modified (e.g. dragged tracks) and are send to the GPU every frame.
To boost
12 matches
Mail list logo
