...and for some reason antialiasing stays enabled anyway. I retract the question.
Cheers, Orson On 02/08/2018 09:01 AM, Maciej Sumiński wrote: > One more question, I have just realized that I disabled antialiasing > when USE_WX_GRAPHICS_CONTEXT is enabled. Is that fine for macOS or > eeschema runs fast enough, so antialiasing is preferred? > > Cheers, > Orson > > On 02/07/2018 06:36 PM, Bernhard Stegmaier wrote: >> … yes, no good. >> It seems to be OK when just panning around. >> But, it gets very laggy while e.g. dragging/moving symbols around (even on a >> not so big schematic I had at hand). >> >> It is fine if you take out the Refresh() quoted below on macOS. >> I didn’t see any obvious things on a quick check with the remaining changes >> (might be due to the fact that crosshair is still disabled on macOS?). >> >> >> Regards, >> Bernhard >> >>> On 7. Feb 2018, at 17:32, Bernhard Stegmaier <stegma...@sw-systems.de> >>> wrote: >>> >>> … USE_WX_GRAPHICS_CONTEXT is on per default on macOS. >>> >>> I will check tonight, but I guess/fear that the part >>> <<< >>> +#ifdef USE_WX_GRAPHICS_CONTEXT >>> + // Screen has to be updated on every operation, otherwise the cursor >>> leaves a trail (when xor >>> + // operation is changed to copy) or is not updated at all. >>> + Refresh(); >>> +#endif >>>>>> >>> will make it slow (might cause double painting every time because of how it >>> is already handled right now without the extra refresh). >>> >>> I’ll report (if no other macOS guy is faster than me… :) ) >>> >>> >>> Bernhard >>> >>>> On 7. Feb 2018, at 15:38, Maciej Sumiński <maciej.sumin...@cern.ch> wrote: >>>> >>>> Two patches to fix some troubles occurring on wxGTK3. The first one >>>> displays a warning when it detects that KiCad is being built against >>>> wxGTK3. The second one makes eeschema functional, just a bit slower when >>>> compared to wxGTK2. The only thing that is really broken is pcbnew >>>> printing, but there are also some other glitches (e.g. black background >>>> in eeschema printing preview, though the actual printouts are ok). >>>> >>>> I have tested the patch under Linux and Windows and noticed no influence >>>> on wxMSW/wxGTK2, as expected. I would love to hear from OSX users that >>>> there are no new issues introduced in the patch. >>>> >>>> Unfortunately, it does not resolve the recent wxpython-gtk3 issue on >>>> Arch Linux. The problem occurs when KiCad is linked against wxGTK2, but >>>> wxPython uses wxGTK3. In such case KiCad loads wxGTK2 libraries on start >>>> and when wxPython is initialized - it tries to load wxGTK3 causing >>>> symbol conflicts. I guess there is not much we can do about it, apart >>>> from detecting such situation and informing the user about the problem >>>> cause. Any other ideas? >>>> >>>> Cheers, >>>> Orson >>>> <0001-GTK3-Display-a-warning-and-enable-wxGraphicsContext.patch><0002-wxWidgets-GTK3-compatibility-fixes-for-eeschema.patch>_______________________________________________ >>>> Mailing list: https://launchpad.net/~kicad-developers >>>> Post to : email@example.com >>>> Unsubscribe : https://launchpad.net/~kicad-developers >>>> More help : https://help.launchpad.net/ListHelp >>> >>> >>> _______________________________________________ >>> Mailing list: https://launchpad.net/~kicad-developers >>> Post to : firstname.lastname@example.org >>> Unsubscribe : https://launchpad.net/~kicad-developers >>> More help : https://help.launchpad.net/ListHelp >> >> > > > > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : email@example.com > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp >
Description: OpenPGP digital signature
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : firstname.lastname@example.org Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp