Window.open should allow you to pick a screen

[adam-lynch]

I guess by passing in a screen (/ screen ID) from the Screen API. The coordinates you give then should be relative to that screen. Should be optional & defaults to the current screen (where the app is placed) / the "primary" one (see #2383).

But then I guess if this was added, then there should also be a function to move a window to another screen (again by passing a screen / ID).

Related: #2178

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[adam-lynch]

Example use case: custom notifications

[adam-lynch]

Looking at what gui.Screen.screens returns again and it seems that the primary screen's bounds.x and bounds.y are 0. Can someone confirm if this is always the case?

EDIT

I actualy meant to post this as a reply to #2383

[Destreyf]

adam, the way that i found works best for detecting the workspace, is by taking the screen with work_area less than bounds. This works on Windows, Mac and Ubuntu 14.04 tested.

[adam-lynch]

@Destreyf But on my Windows setup here the taskbar goes across all screens. Also, a colleague told me yesterday that the Mac menu / context bar can be on multiple screens since Mavericks (previously used to denote the primary screen).

[matthiasg]

@adam-lynch if your taskbar really goes across all screens (e.g start button all the way on the left monitor, clock all the way on the right), then your graphics driver is setup as one big monitor and is not really using multi monitor support of windows per se. Its just one big desktop from the perspective of the applications. This would affect every app (such as e.g. lightroom) that has multi monitor features. This mode in the graphics card settings often doesnt make any sense.

[adam-lynch]

@matthiasg No, my starts button is on every screen and the clock is on the middle screen. This is a Windows feature.

[adam-lynch]

[matthiasg]

then you have multiple taskbars .. that's ok of course then you indeed have multiple true screens … i understood it such that you have one long taskbar (which would be a driver feature).

But in that case there isn't much of an issue since you can position a window globally … e.g setting it to -1000,0 would position it on the left of the primary screen ..

in combination with screen geometry that would get you started..

admittedly it would be extremely helpful to move this very common use cases into node-webkit to prevent people from re-implementing this over and over .. or a common external library that does the calculation and were required into the app could help too..

From: Adam Lynch
Sent: ‎Tuesday‎, ‎October‎ ‎28‎, ‎2014 ‎11‎:‎34‎ ‎AM
To: rogerwang/node-webkit
Cc: mgt576@gmail.com

@matthiasg No, my starts button is on every screen and the clock is on the middle screen. This is a Windows feature.

—
Reply to this email directly or view it on GitHub.

[adam-lynch]

But in that case there isn't much of an issue since you can position a window globally … e.g setting it to -1000,0 would position it on the left of the primary screen ..

Not always. See #1152.

[matthiasg]

The other ticket is talking about off screen .. Which might mean outside the screen area as defined by all monitors.. It might also mean off the primary screen.. Do you have more info on that ?

-----Original Message-----
From: "Adam Lynch" notifications@github.com
Sent: ‎28.‎10.‎2014 17:46
To: "rogerwang/node-webkit" node-webkit@noreply.github.com
Cc: "matthiasg" mgt576@gmail.com
Subject: Re: [node-webkit] Window.open should allow you to pick a screen(#2384)

But in that case there isn't much of an issue since you can position a window globally … e.g setting it to -1000,0 would position it on the left of the primary screen ..
Not always. See #1152.
—
Reply to this email directly or view it on GitHub.=

[adam-lynch]

I created #2391 myself. To me, screen is an individual screen, the same meaning the screen API uses.

[matthiasg]

I will try to recreate that with the 0.11 rc1 when I can then .. I will need some sensible multi monitor functionality relatively soon as we are starting to port our current medical image viewing application. I would assume a common library on top of NW would make sense, but that does require that positioning windows across all screens works of course

-----Original Message-----
From: "Adam Lynch" notifications@github.com
Sent: ‎28.‎10.‎2014 20:02
To: "rogerwang/node-webkit" node-webkit@noreply.github.com
Cc: "matthiasg" mgt576@gmail.com
Subject: Re: [node-webkit] Window.open should allow you to pick a screen(#2384)

I created #2391 myself. To me, screen is an individual screen, the same meaning the screen API uses.
—
Reply to this email directly or view it on GitHub.=

[donaldpipowitch]

Maybe related #180? Its a little bit confusing, because most terms sound so similar (window, screen, desktop, monitor...)

[fritx]

// Calculating for new win screen/position
const depWin = global._wins['home'] ||
  global._wins['login'] || win
const winCX = depWin.x + depWin.width / 2
const winCY = depWin.y + depWin.height / 2
const curScr = _.find(screens, (scr) => {
  const { x, y, width, height } = scr.bounds
  return winCX >= x && winCX < x + width &&
    winCY >= y && winCY < y + height
}) || screens[0] // todo: Some more calculating
const wrkCX = curScr.work_area.x + curScr.work_area.width / 2
const wrkCY = curScr.work_area.y + curScr.work_area.height / 2
opt.x = wrkCX - opt.width / 2
opt.y = wrkCY - opt.height / 2

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.