[awesome bugs] #1080 - awful.rule cannot move mplayer to second screen

2013-02-26 Thread awesome

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task is now closed:

FS#1080 - awful.rule cannot move mplayer to second screen
User who did this - Julien Danjou (jd)

Reason for closing: Won't fix
Additional comments about closing: Oldest bug in the world! mplayer does a 
configurenotify after the initial mapping, so it's impossible to do that. Bad 
mplayer.
Use mplayer -xineramascreen instead and blame the mplayer devs.

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1080

You are receiving this message because you have requested it from the Flyspray 
bugtracking system.  If you did not expect this message or don't want to 
receive mails in future, you can change your notification settings at the URL 
shown above.

--
To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.


[awesome bugs] #1080 - awful.rule cannot move mplayer to second screen

2013-02-26 Thread awesome

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has been re-opened:

FS#1080 - awful.rule cannot move mplayer to second screen
User who did this - Julien Danjou (jd)

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1080

You are receiving this message because you have requested it from the Flyspray 
bugtracking system.  If you did not expect this message or don't want to 
receive mails in future, you can change your notification settings at the URL 
shown above.

--
To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.


[awesome bugs] #1080 - awful.rule cannot move mplayer to second screen

2013-02-26 Thread awesome

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1080 - awful.rule cannot move mplayer to second screen
User who did this - Julien Danjou (jd)

--
Oldest bug in the world! mplayer does a configurenotify after the initial 
mapping, so it's impossible to do that. Bad mplayer.
Use mplayer -xineramascreen instead and blame the mplayer devs.
--

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1080#comment3470

You are receiving this message because you have requested it from the Flyspray 
bugtracking system.  If you did not expect this message or don't want to 
receive mails in future, you can change your notification settings at the URL 
shown above.

--
To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.


[awesome bugs] #1080 - awful.rule cannot move mplayer to second screen

2013-01-04 Thread awesome

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - Alex Rez (realx) 


Attached to Project - awesome
Summary - awful.rule cannot move mplayer to second screen
Task Type - Bug Report
Category - awful
Status - Unconfirmed
Assigned To - 
Operating System - All

Severity - High
Priority - Normal
Reported Version - 3.5
Due in Version - Undecided
Due Date - Undecided
Details - version 3.4 works fine, but 3.5 fails:
   { rule = { class = MPlayer },
properties = {
floating = true,
screen = 2
}},


More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1080

You are receiving this message because you have requested it from the Flyspray 
bugtracking system.  If you did not expect this message or don't want to 
receive mails in future, you can change your notification settings at the URL 
shown above.

--
To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.