...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 run
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 wh
Ok, many thanks for the reports. I will simply wrap the Refresh() with
#ifdef GTK3, as apparently it is not required anywhere else.
Regards,
Orson
On 02/07/2018 08:22 PM, Wayne Stambaugh wrote:
> On 2/7/2018 2:07 PM, jp charras wrote:
>> Le 07/02/2018 à 18:36, Bernhard Stegmaier a écrit :
>>> … y
Oh wait, I do.
The whole box already says “(not supported in Legacy graphics)”.
So we could remove the “not in legacy” disclaimer for Mac, and reverse the
checkbox sense for non-Mac (so it would say something like “Hide crosshairs for
selection tool” or something).
> On 7 Feb 2018, at 20:56,
Well, except on OSX, where the legacy canvas didn’t support it.
So turning on the checkbox isn’t supported in Mac-legacy, while turning off the
checkbox isn’t supported in other-legacy.
I haven’t the foggiest idea how to communicate that succinctly.
> On 7 Feb 2018, at 20:39, Wayne Stambaugh
The crosshair behavior is canvas dependent. In the legacy canvas, the
crosshairs (full screen or small) are always shown. In the modern
canvases, the crosshairs are only show when a tool is active and the
option is disabled. Enabling the option makes the modern canvas
behavior the same as the le
Oh wait, bells are ringing.
The disclaimer on the checkbox is OSX-only. Other platforms support it even in
legacy, don’t they?
> On 7 Feb 2018, at 20:28, Wayne Stambaugh wrote:
>
> I just looked and there is no mention of legacy or modern in the
> checkbox string. There is a "not supported
I just looked and there is no mention of legacy or modern in the
checkbox string. There is a "not supported in legacy graphics" note in
the grid options but not the crosshair setting.
On 2/7/2018 2:24 PM, Jeff Young wrote:
> We already did. Well: “Always display crosshairs (not in Legacy)”, anyw
We already did. Well: “Always display crosshairs (not in Legacy)”, anyway.
> On 7 Feb 2018, at 19:21, Wayne Stambaugh wrote:
>
> On 2/7/2018 1:54 PM, jp charras wrote:
>> Le 07/02/2018 à 19:44, Wayne Stambaugh a écrit :
>>> If you are using a gal canvas, the only time you see the cross hairs i
On 2/7/2018 2:07 PM, jp charras wrote:
> Le 07/02/2018 à 18:36, Bernhard Stegmaier a écrit :
>> … 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
On 2/7/2018 1:54 PM, jp charras wrote:
> Le 07/02/2018 à 19:44, Wayne Stambaugh a écrit :
>> If you are using a gal canvas, the only time you see the cross hairs is
>> when a tool is selected. This is true of even the small cross hairs.
>
> Yes, but if in Preferences/Display Options you enable "A
Le 07/02/2018 à 18:36, Bernhard Stegmaier a écrit :
> … 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 ma
Le 07/02/2018 à 19:44, Wayne Stambaugh a écrit :
> If you are using a gal canvas, the only time you see the cross hairs is
> when a tool is selected. This is true of even the small cross hairs.
Yes, but if in Preferences/Display Options you enable "Always display
crosshairs" you should have
the
If you are using a gal canvas, the only time you see the cross hairs is
when a tool is selected. This is true of even the small cross hairs.
On 2/7/2018 1:41 PM, Bernhard Stegmaier wrote:
> Yes, did see the button (synced today).
> But it didn’t seem to change anything.
> Where should I see it?
>
Yes, did see the button (synced today).
But it didn’t seem to change anything.
Where should I see it?
> On 7. Feb 2018, at 19:39, Jeff Young wrote:
>
> The crosshairs should be available again in a current build. Do you see the
> toolbar button on the left?
>
>> On 7 Feb 2018, at 17:36, Bernh
The crosshairs should be available again in a current build. Do you see the
toolbar button on the left?
> On 7 Feb 2018, at 17:36, 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 (ev
… 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 r
… 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
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 ar
19 matches
Mail list logo
