Item bubble size/coordinates not respecting resolution about laserweb4

[cojarbi]

Maybe its the same issue but as the bubble is not scaling then it gets in the way preventing at some point from seeing whats behind. Imagine the user it trying to align or similar.

[tbfleming]

Very odd. Which browser and OS? Here's what it's supposed to do. (Chrome 54 on Windows 10):

[cojarbi]

Indeed. As i see the intended above, mine is not sticking to the corner but floating around stuck to the left bottom corner of the path
OSX 10.12
Chrome Version 54.0.2840.98 (64-bit)

[tbfleming]

Here's what it's currently supposed to do:

• Browser zoom affects all text and controls, except the grid text
• Workspace zoom, pan, and rotate affect grid, paths, images, animated selection border, gcode preview, laser preview
• Upper-right corner of bubble is attached to lower-left corner of the selection, but it doesn't leave the workspace area

[cojarbi]

Aditional test on OSX
Chromium does not the grid
Safari does not load the page at all

Both have webgl enabled and can open LW3

[tbfleming]

Chromium surprises me; it should behave exactly like Chrome. Safari is a major PITA to support; Apple's letting much of it rot.

[kaosat-dev]

Agreed on the sentiment , I can try it & bugfix at least on Safari on mac if that helps @tbfleming

[tbfleming]

LW4 will target Chrom(ium) only, since it's available everywhere except on devices we won't support anyway (iOS). Any help with the Chrome(ium) issues on OSX would be great!

[kaosat-dev]

Ok I'll install & take a look

[kaosat-dev]

Chrome: (54.0.2840.98)
Chromium:(57.0.2946.0)
So if I get that right, these both have the issue ? Bubble supposed to stay in the corner of the grid right? (same at any scale btw)

[kaosat-dev]

Just a semi useless fyi , but the problem in Safari is just its lack of support for the Fetch api

[kaosat-dev]

I'll dig deeper into what causes the issue tomorrow if you don't mind

[cojarbi]

Not sure if its related but im getting serious computer freezes and lock ups on OSX Chrome.

[kaosat-dev]

@cojarbi do you have a few steps/sample files that you used to reproduce ?

[cojarbi]

@kaosat-dev bellow the file i was using. Load the file and open the 2 operations as above filling the fields, in less than a minute i get the same result
s
LaserWeb4.svg.txt

[kaosat-dev]

@cojarbi ok thanks ! I can at least partially reproduce those issues, memory/CPU is high and crashed chrome when trying to close LW4, will investigate

Is this still a problem?

[cojarbi]

This should be moved to osx issues ⁣Ariel Yahni​

…

On Jan 13, 2017, 14:44, at 14:44, Peter van der Walt ***@***.***> wrote: Is this still a problem? -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #54 (comment)

[cojarbi]

I think I have tracked this down to High resolution Retina equiped apple machines.

https://www.khronos.org/webgl/wiki/HandlingHighDPI

[tbfleming]

@cojarbi The fix for #349 might affect this. Could you retest?

[cojarbi]

Folved by copying machine profiles from another instance ( old ) and ITS A MIRACLE, that solved the sizing / clicking on grid

…

On Sun, Jun 18, 2017 at 6:00 PM, Ariel Yahni ***@***.***> wrote: Im still getting the same error from yesterday, cant compile or npm start On Sun, Jun 18, 2017 at 5:42 PM, Todd Fleming ***@***.***> wrote: > @cojarbi <https://github.com/cojarbi> The fix for #349 > <#349> might affect this. > Could you retest? > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#54 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/APrsFtyA1kCqx4tx_-kft4hcFOWbe944ks5sFafCgaJpZM4LHwox> > . > -- Ariel Yahni

-- Ariel Yahni

[cojarbi]

I feel normal again!!!! Tx Sir