Aurora 4x

VB6 Aurora => Installation => Topic started by: hiphop38 on November 27, 2016, 10:12:30 PM

Title: Population and Production page issue
Post by: hiphop38 on November 27, 2016, 10:12:30 PM
So I have recently tried to start playing Aurora on my Laptop that I just recently got.

I have installed Aurora as I usually would for my desktop.  Everything works, as in no error messages appear when a page is opened etc. . .  but whenever I try to select a different colony on the population and production page, the list essentially freezes.  However, the rest of the page still works.  All the tabs work, pages work, just the colony table freezes and I cannot change colony. 

It is confusing as I have never seen it happen before and I have not heard of anything like this happening before.

Does anyone know of this issue and or have a solution?
Title: Re: Population and Production page issue
Post by: DIT_grue on November 27, 2016, 10:50:05 PM
First thing to check is to turn off any drivers for touchscreen etc. - VB6 Treeview controls have no clue how to deal with them.
Title: Re: Population and Production page issue
Post by: GodEmperor on November 28, 2016, 04:40:46 AM
And disable Windows on screen keyboard, Aurora gets all wonky with its on.
Title: Re: Population and Production page issue
Post by: 83athom on November 28, 2016, 07:26:04 AM
This has been asked and answered many times, and is on the FAQ (http://aurora2.pentarch.org/index.php?topic=1194.0). Please re-read the rules of posting (http://aurora2.pentarch.org/index.php?topic=2043.0).
Title: Re: Population and Production page issue
Post by: hiphop38 on November 29, 2016, 12:07:44 PM
I understand that I shouldn't be posting here, but I thought id follow up with my solution.

Interestingly enough, simply turning the touch screen off did not fix the issue.  It kept doing that, UNTIL I selected a colony WITH the on screen keyboard up.  (I know, weird)
After that I could close the on screen keyboard and proceed as normal.  This even worked with the touchscreen on, until I pressed the next turn button.  Sadly I have not had time to test all the permutations of this but I thought it would be interesting to others who may have a similar issue.