EmperorFool
Deity
Both the laid-out borders and the highlight border when placing a new city have separate transparency (called brightness thinking more people would understand that better) controls on the General options tab.
Both the laid-out borders and the highlight border when placing a new city have separate transparency (called brightness thinking more people would understand that better) controls on the General options tab.
- CTRL + X: Show/hide dotmap
- ALT + X: Toggle dotmap edit mode
Open the BUG options screen (ALT + CTRL + O) and check the third column on the first tab. Make sure that the STRATEGY LAYER is Enabled.
If that still doesn't solve it, after hitting ALT + X, alt-tab out of the game (or exit) and open the file "C:\Documents and Settings\<User>\My Documents\My Games\Beyond the Sword\Logs\PythonErr.log". If it isn't empty, post it here. If it's empty, post PythonDbg.log in that same folder.
How are you getting the SVN versions? Are you using TortoiseSVN or grabbing the ZIP snapshots? If the latter, perhaps you got the snapshot from before I committed as I think Alerum's PC posts a new one after midnight PST each night.
Don't forget you always have ALT + S for making signs.
I wholeheartedly agree about splitting the tabs now. Think you can tackle it, or should I?
[...]
Only problem is that the sliders have no fixed width and extend themselves across the whole screen.
Another thing is that they show no value unlike the FOV slider at the main interface.
Cool.Heh, sweet. I can probably add a width pretty easily.
This will be harder; possible, but harder. Is it really worth it? Do you really need to see the numerical value? For an example, take a look at the Sound tab of the normal options screen. None of those sliders display their values.
But I was thinking of some other options that use dropdown menus at the moment like the LineHeight and the MaxPlayers options at the scoreboard tab.
Maybe you could "recycle" ruff's code from the FOV slider.
I would strongly advise against using any of ruff's code for recycling purposes ... unless you just like messy, nonsensical code!Maybe you could "recycle" ruff's code from the FOV slider.
Just figured out that you set "expanding" to "True" for the sliders. Setting it to "False" made them a lot shorter but they are still pushing the other column to the far right.
@Tick Marks: For each bar? Are you serious? That's a lot of micro-management.
Hmm, I don't think the slider is causing that. The column itself is probably set to expanding. Other columns work fine, so once you commit I can take a look at it to see if there's something that stands out. If you temporarily remove the two sliders (comment them out), does it still expand the first column?
Do you realize there are only three bars with ticks marks? My thought is that if you split it into two options, you may as well split it into three. Then again, I can see having a "Tick Marks" option on each of the tabs that controls all bars on that tab. I'm fine either way. Do you need me to split the options and do the Python, or can you tackle that as well?
. . . or we apply the Tick Marks to all other bars as well (Great General/Person Progress Bar at the main interface and GP/culture bar at the city screen).
(btw: Shouldn't we get our discussion to somewhere else, like the Development thread?