Oh cool. I’ll look into it….
> On 26 Jul 2019, at 14:57, Wayne Stambaugh wrote:
>
> I implemented regular expression search method in EDA_ITEM but I never
> finished hooking everything up at the UI level. So unless someone
> removed it, it should still be there.
>
> Cheers,
>
> Wayne
>
>
I implemented regular expression search method in EDA_ITEM but I never
finished hooking everything up at the UI level. So unless someone
removed it, it should still be there.
Cheers,
Wayne
On 7/26/19 3:41 PM, Jeff Young wrote:
> I went with something similar to Seth’s proposal, only based on
I went with something similar to Seth’s proposal, only based on Eeschema’s find
(so no regular expressions yet).
Most of the workings are down in EDA_ITEM, so if we add regex matching we’ll
get it in both Eeschema and Pcbnew.
Cheers,
Jeff.
> On 26 Jul 2019, at 13:11, Seth Hillbrand wrote:
>
On 2019-07-26 14:39, Jeff Young wrote:
PCBNew’s current Find does a match against the whole string. I think
it would be more intuitive with a ‘*’ in front and back of the search
string (so that it finds partial matches).
Any other opinions?
___
personally I'd like being able to use full regular expressions, so that
the new user can use the asterisk, more advanced users can use more complex
expressions to better filter the results.
Il Ven 26 Lug 2019 20:45 Jon Evans ha scritto:
> Another way to solve this is the Google approach:
Another way to solve this is the Google approach: match internal
substrings unless you put the search term in "quotes" in which case only
match complete words.
On Fri, Jul 26, 2019 at 2:43 PM Kliment (Future Bits)
wrote:
> One issue I can think of offhand is that searching for "R2" would find
One issue I can think of offhand is that searching for "R2" would find
"R21" and searching for "1uF" would match "0.1uF", both of which would
be annoying. Maybe an "allow partial matches" checkbox?
On 26.07.19 20:39, Jeff Young wrote:
> PCBNew’s current Find does a match against the whole string.
PCBNew’s current Find does a match against the whole string. I think it would
be more intuitive with a ‘*’ in front and back of the search string (so that it
finds partial matches).
Any other opinions?
___
Mailing list:
There’s a bug that you can’t change layers while routing. Turns out it’s
really that you can’t execute most hotkeys found on ed keys while
running a tool.
The problem is that wxEVT_CHAR_HOOK doesn’t do the key translation properly.
wxEVT_CHAR does, but we only get to that if we skip the
A “free” or “stitching” via (ie: one not connected to tracks), or one in the
middle of a track?
I don’t believe dragging of free vias ever worked (although it is fixed in 6.0).
> On 26 Jul 2019, at 03:41, Dino Ghilardi wrote:
>
> On version tagged 5.1.3 I'm unable to drag vias with the "D"
Hi Thomas,
I tested your patches and they seem to work as advertised. I don't have
a copy of Eagle to confirm that the conversions are correct. I can only
test to see if the import is as expected with your patches. I went
ahead a merged them into the master branch. We can always revert them
It looks like there are some issues with installing wx 3.1, although it
should still use 3.0.
fre. 26. jul. 2019 08.04 skrev Holger Vogt :
> There are no upgrades of the builds at
> https://kicad-downloads.s3.cern.ch/index.html?prefix=windows/testing/5.1/
> since July 14.
>
> Could please
On version tagged 5.1.3 I'm unable to drag vias with the "D" shortcut
(drag 45 degrees), is it a bug or a new feature? (I did not see any
option like "consider all vias locked while dragging", so I suppose this
behaviour is not intended).
Do I have to file a bug report on launchpad?
Cheers,
There are no upgrades of the builds at
https://kicad-downloads.s3.cern.ch/index.html?prefix=windows/testing/5.1/
since July 14.
Could please somebody take care to switch this on again?
Holger
___
Mailing list:
14 matches
Mail list logo
