Please attempt to not derail a thread. This thread is about making the default canvas default or not about remapping.
About remapping it is much more helpful if you create a bug report and include a project to test against. Den 3. jan. 2018 10.23 AM skrev "André S." <list.dev.ki...@nospamail.de>: > Hi, > > ok, I downloaded and installed the latest nightly. > What a nightmare. :D > I tried to open my schematic. It told me that it will be transferred to > the new format and also showed a rescue dialog. > It tries to map the symbols to the symbol library table. Afterwards it > could not find the symbols in the (new) symbol lib table and therefore all > symbols were broken. (This may be due to the fact that the nightly comes > without libraries? I installed the nightly in a fresh directory, not the > directory of 4.0.7.) > I hope there will be a test for the release version before roll-out > (Release Candidate) so that such issues are addressed? > > The PCB editor still shows a white screen when switching to Cairo, but > definitely for a shorter time(1..2 seconds). > Each canvas renders the texts differently. > 'G' works now in OpenGL/Cairo, but differently than in Legacy (moves > connection point of segments vs. whole segment). 'G' in OpenGL acts like > 'M' in Legacy. > 'D' works in Legacy, but does not stop at 90° like in OpenGL when dragging > a 45° bend segment. When moving further than 90° distance it draws crossing > lines and expands the segment. > > Component Values are not displayed regardless of canvas, even Legacy does > not show them any more. > Bug: https://bugs.launchpad.net/kicad/+bug/1741015 > > *Observations*: Some icons have changed, most I like but not all. Symbol > Editor Icon is way to busy, too much color where not needed. Same for > Library Editor icon. Removing the background color/pattern would help a lot. > I found the old Annotation icon more logical, it told in one picture what > it does. The new one may be an editor icon for all it shows. > > Regards, > André > > PS: I appreciate all the improvements, even if my comments may sound too > negatively. ;) > e.g. the new options for graphical lines in the schematics. Useful > addition there would be to have an option to set the default for this (type > and color). :) > > Am 2018-01-02 <20%2018%2001%2002> um 18:28 schrieb José Ignacio: > > > > On Tue, Jan 2, 2018 at 11:18 AM, André S. <list.dev.ki...@nospamail.de> > wrote: > >> Hi everyone, >> >> I want to add from a users view: >> In the current KiCad 4.0.7 (Windows 64 bit) you can't drag traces in >> OpenGL/Cairo, only in legacy. (With this I mean: move a segment of a trace >> and it stays attached to the other segments of the trace (Hotkey: 'G')). >> Hotkey 'M' moves segments in OpenGL but moves 'connections' in Legacy >> (segments stay connected). >> More often than not I need the behaviour of Legacy and not that of the >> OpenGL canvas. >> >> In GAL the key to move connections is D, which allows you to drag traces > using the push and shove algorithm. Why is it this not G? I have no idea. > > >> Values are not displayed in OpenGL/Cairo, only in Legacy. >> > > That is odd, is there a bug report for that? > > >> And "transparency" is better in Legacy. With only 2 layers you can see >> the traces on the bottom layer better than in OpenGL/Cairo. >> > > This was broken recently when the RGBA setting was added. It used to be > that all layers would have 80% transparency by default. this probably > should be fixed again, I personally prefer to set the transparency even > lower for inner layers too. This is all user settable in the nightlies. > > >> >> Just for this few reasons I still use Legacy more often than OpenGL when >> modifying an existing PCB design. >> >> From my view OpenGL is nice because you can manipulate single items >> (segments of traces) better/more comfortably than in Legacy. And initial >> layout work feels smoother. >> >> Just my 2 cents. :) >> >> Happy new year, >> André >> >> PS: as a side note: When I switch from "Standard/Legacy" or OpenGL to >> Cairo the PCB view goes white and only after a few seconds displays the >> PCB. In the other direction there is no delay. >> > > Performance was greatly improved in GAL in the latest nightlies, did you > try them or just the GAL as seen in 4.0.7? > > >> >> >> Am 2017-12-31 <20%2017%2012%2031> um 22:28 schrieb Jon Evans: >> >> For your consideration, a patch is attached that implements the above. >> >> >> On Sun, Dec 31, 2017 at 2:24 PM, Jon Evans <j...@craftyjon.com> wrote: >> >>> I think that getting automatic OpenGL detection and recovery working for >>> 5.0 might be ambitious. >>> Maybe Chris can detail what the next steps are for his approach there, >>> but in case we want to push that to a later release, here's what I propose: >>> >>> 1) Rename the View menu options based on my proposal "Legacy", "Modern >>> (Accelerated)", "Modern (Fallback)" >>> 2) Change PCB_BASE_FRAME::SwitchCanvas to save the canvas config value >>> after calling UseGalCanvas() rather than before. >>> 3) Show a first-run dialog like the mockup in my earlier email, IF >>> canvas is not OpenGL and the dialog has not been shown before >>> 44) If user clicks "yes" in the first run dialog, then: >>> (a) set the config value to prevent the dialog from showing again, >>> (b) Set the canvas config setting to Cairo (but don't switch the GAL >>> to Cairo), then >>> (c) switch to OpenGL canvas using SwitchCanvas() >>> >>> That way, if the app crashes in step 4c, it should come back up as Cairo >>> on the next launch (assuming we crash right away when trying to set up the >>> canvas) >>> >>> Any concerns with the above? >>> >>> -Jon >>> >>> >>> >>> On Sun, Dec 31, 2017 at 1:55 PM, Jeff Young <j...@rokeby.ie> wrote: >>> >>>> +1 >>>> >>>> No menu items. Just a checkbox for Enable Hardware Acceleration in >>>> Preferences. >>>> >>>> On 31 Dec 2017, at 18:36, Andy Peters <de...@latke.net> wrote: >>>> >>>> - In the case of graphics glitches, inform the users in the FAQ/Manual >>>> that they can fall back to software renderer in the View menu. >>>> - Don't use the term 'canvas' or 'view'. Just 'Enable HW acceleration’. >>>> >>>> >>>> I like that. The fewer technical/programmer terms, the better. >>>> >>>> >>>> >>>> _______________________________________________ >>>> Mailing list: https://launchpad.net/~kicad-developers >>>> Post to : kicad-developers@lists.launchpad.net >>>> Unsubscribe : https://launchpad.net/~kicad-developers >>>> More help : https://help.launchpad.net/ListHelp >>>> >>>> >>> >> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> >> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> >> > > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
