Hi, I seem to be progressing along. I now have a handle on the GUI and adding a new key stroke - I have coded up Alt-D for multi-track dragging for now - and I am examining ROUTER_TOOL::performDragging and understanding how this works in detail all the way down to LINE::dragCorner45 and all the other methods around it. There is quite a lot here to understand and how they all interact, but slowly I am understanding the complexities and how to make things work.
My top level code is a copy of ROUTER_TOOL::performDragging and I am calling my top level ROUTER_TOOL::performDraggingMultiTrack. I am expecting to use all the same methods as used by performDragging, except only working on the selected traces in 45 deg mode, and highlight mode. What I would like is to use printf() to output some debug information. I see that Tom uses this method - as the code is sprinkled with printf()'s behind #ifdef's. What I am not too sure on is how to get to the stdout on a gui application. I currently start pcbnew from within MS Visual Studio. I have looked around for a window that may have stdout with no luck. Do I need to start pcbnew from the command line? When I go to the pcbnew build directory (..\build\x64-Debug\pcbnew) and try to run pcbnew it complains about python not being installed. I believe that is because the python path is not set correctly. I then started playing with the (install)(bin\pcbnew.exe) to see if this version can be run from the command line - as I started to assume that the (pcbnew\pcbnew.exe) version was for running in the VS ide. When I run (bin\pcbnew.exe) from within VS ide or command line I get several system error screens saying 'The code execution cannot proceed because wxms32ud_html_vc_custom.dll was not found. Reinstalling the program may fix this problem." Several of these pop up and substitute _html_ for _code_, _aui_, and _net_. In VS under the Build menu, I saw an option 'Install kicad'. I press this, and I get a Install succeeded. But running from cmd line or VS still barfs the code execution errors above. Hmm, what am I missing? I can only currently run my compiled version of pcbnew from VS (pcbnew\pcbnew.exe). How to get to stdout to see printf? I am assuming once I can run it from cmd line that I should then see stdout. Is there an install process that I am missing to use pcbnew from the command line? Thanks Stuart On Monday, July 3, 2023 at 5:58:32 PM UTC+1 Stuart Tyler wrote: > Thank you all for those pointers. > > I suspected as much, and so it looks like off to cpp land I go. > > Thank you Tomasz Wlostowski for the pointer into the code base where to > start looking for the implementation. Agree - I am only attempting "mark > collisions" mode. Personally I never use push/shove or walk around when > routing - by never I mean very rarely. The modes just destroy the good look > and feel of a PCB. > > Thanks for the pointer Eeli Kaikkonen to the component/part dragging > issue. I did observe this issue too on the drag when I played with pcbnew, > but that is not something that I want to tackle first up. That is one nasty > problem, of which I am not interested in attempting to solve right now. The > nastiness comes from footprints can have many trace orientations and what > to do to drag the component is non-obvious. > > Thanks > Stuart > > -- You received this message because you are subscribed to the Google Groups "KiCad Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to devlist+unsubscr...@kicad.org. To view this discussion on the web visit https://groups.google.com/a/kicad.org/d/msgid/devlist/921a98a2-b96c-450c-859d-0de8caec43c2n%40kicad.org.
