[Wesnoth-bugs] [bug #25299] UTBS/Performance: unit movement over shroud is laggy

[Severin Glöckner]

Follow-up Comment #5, bug #25299 (project wesnoth):

I did build wesnoth again with your last commits.

Then it works. Only when the Hexagon is active it's bad.
And hexagon + alternative terrain drawing works quite good, but it's not the
same "good" like if all is disabled.

___

Reply to this item at:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs

[Wesnoth-bugs] [bug #25303] workspace switching in fullscreen mode

[Severin Glöckner]

URL:
  

 Summary: workspace switching in fullscreen mode
 Project: Battle for Wesnoth
Submitted by: shiki
Submitted on: Tue 15 Nov 2016 12:20:22 PM UTC
Category: Bug
Severity: 4 - Important
Priority: 5 - Normal
  Item Group:  None of the others
  Status: None
 Privacy: Public
 Assigned to: None
Originator Email: 
 Open/Closed: Open
 Discussion Lock: Any
 Release: 1.13.6+dev
Operating System: Archlinux Win10

___

Details:

One of the good things from the sdl2 movement is that it's now possible to
switch workspaces while you use fullscreen mode. For wesnoth that's in
particular good, since you have to wait between the rounds, and games often
take hours.
However, there are some bugs which should be fixed before 1.14:


When using fullscreen mode, by switching to another workspace and back,
wesnoth gets often, but not in every case, minimized.

E.g try this:
Use key combinations for workspace switching, possibly
ctrl+alt+(up/down)/(left/right) or ctrl+F1/F2/F3/F4
Start wesnoth on the second workspace.
Switching to the third and back is fine.
Switching to the first and back minimizes wesnoth.
(or the other way around)


Another possibility of switching workspaces are kind of overview modes.
In gnome 3, that's what you get with the [win] key.
In kde 5 exist many similar such modes (grid, cube, zylinder, ball, and more),
one of them is availaible with ctrl+F11, two others with ctrl+F9/F10. *
Windows 10 has as well sth. like this.

The problem is the same here. But what do these overview modes show when the
window got minimized (due to switching the workspace forth and back in
overview mode)?
 => see picture 1 & 2. When choosing the wesnoth windows again, everything is
fine.
When the wesnoth window is not minimized, then the wesnoth window looks normal
in the pverview, without broken map.


With much workspace switching something like that can happen too:
 => in gnome: see picture 3
 If I click away the message, all works fine.
 In kde I didn't happen to get such a message, maybe kde is more tollerant
there.
 In windows 10 I managed somehow to get a similar message (tough windows
doesn't allow me to click away the message and continue the game), but I can't
reproduce it. The key combination to switch workspaces in windows 10 is
ctrl+win+(right/left).


 
* "Allow Applications to block compositing" must be disabled in the system
settings -> hardware -> display -> compositor



___

File Attachments:


---
Date: Tue 15 Nov 2016 12:20:22 PM UTC  Name: picture_1(gnome).jpg  Size: 277kB
  By: shiki


---
Date: Tue 15 Nov 2016 12:20:22 PM UTC  Name: picture_2(kde).jpg  Size: 169kB  
By: shiki


---
Date: Tue 15 Nov 2016 12:20:22 PM UTC  Name: picture_3.jpg  Size: 432kB   By:
shiki



___

Reply to this item at:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs

[Wesnoth-bugs] [bug #25299] UTBS/Performance: unit movement over shroud is laggy

[Daniel]

Follow-up Comment #4, bug #25299 (project wesnoth):

> Without minimap terrain drawing it's as bad as with. 

Hm and when youd deactivate all the minimaostuff (to that all the minmap
buttons (except zoom) are 'blue')

___

Reply to this item at:

  

___
  Nachricht gesendet von/durch Gna!
  http://gna.org/


___
Wesnoth-bugs mailing list
Wesnoth-bugs@gna.org
https://mail.gna.org/listinfo/wesnoth-bugs