Home Trending Latest threads New posts Developer diaries

Double-clicking Ports

Jump to latest Follow Reply
  • We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
U

unmerged(133722)

Second Lieutenant
2 Badges
Feb 2, 2009
113
0
  • Europa Universalis III
  • Europa Universalis III Complete
Does anyone else have consistency problems with the Double-Click to enter Port feature? Especially with the Home Port, the double-click functionality is very intermittent. Sometimes even a single click takes many tries before it registers. There is also a crazy amount of time allowed between clicks. What I am seeing is that if I rapid-double-click (like any power-computer user would), it never registers the double. If I click, wait a second or two, and then re-click, it accepts the double-click.

Does anyone else notice this? Or is it just me?
 
There appears to be one or more memory leaks in this game. The mouse response is sludgy at the best of times. I keep getting the help associated with the window when I am trying to click on the x to close the window.
 
I only have the demo (so far) and I have incredible problems clicking on the port. In the port, in the ledger, no problem at all. Just the port on both computers the demo is on.
 
Never happened to me. Maybe when the port is at the edge of the screen?
 
delra said:
Never happened to me. Maybe when the port is at the edge of the screen?
Click to expand...

That certainly makes the problem worse, however, even with the port selected, a double-click does not always register. If I have the game on Pause, it is more consistent.

The pause comment sheds light on a game-wide UI issue. The game, and any and all software applications, need to respond to user actions IMMEDIATELY. That means the first thing you do is communicate to the user that their action was received (status text, change the icon, flash a button, whatever...). What I notice all over this game is that the action is received, and the screen freezes (or else nothing happens). Then the result of your action is shown. Bad! This makes the user click again, and again, or click somewhere else, or wonder if they have the game paused, or wonder if the game crashed..... it's very simple - communicate to me first that you received my request, and then do whatever you need to do to accomplish my request.

Another example of this is the AutoSave. There is no indication that the game is saving, the bloody screen just freezes, sometimes up to 8 seconds! That's horrible, horrible, programming, guys...come on.
 
You must log in or register to reply here.
Top Bottom
Back