Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Forum Replies Created

Viewing 1 post (of 1 total)
  • Author
    Posts
  • in reply to: Problem With 8.2 #30301
    jbbarnes
    Member

    I experienced the same behavior as soon as I installed the paid version. I had used the community version for about five months and decided to purchase it yesterday. The autocomplete lags behind to the point that it has to be turned off. I'm running a quad-core 6GHz CPU and Windows 7, and it can take eight to ten seconds for the autocomplete to catch up with my typing.

    I was not able to locate a TAGS directory under my profile.

    Also, I noted that the setup program wanted to install to the same folder the Community version was in. I said okay to that, but wondered if it might cause any problems.

    Thanks.

    'peterlaursen' wrote on '06:

    1) Please try to turn off the Autocomplete-feature and see if it is related to this?

    2) Also please tell what version you upgraded from.

    3) Do you happen to use NOD security software from ESET? Anyway also please try to turn off temporarily what you have of the kind.

    One possibility that you have upgraded from a very early version supporting Autocomplete.  At that time corruption of the Autocomplete database could occur as we did not use transactions when writing to it. If turning off Autocomplete solves this issue then please delete or rename the TAGS folder storing those database (in your user profile ('AppData' folder). If you need more help to locate the folder please tell the exact Windows version you are using. 

    Also keywords are stored in a SQLite database. Do you have a 'keywords.db' file in installation folder (and from last install) ? If not try to turn off security softwares while installing. 

    It is not a known issue and we have no similar reports except that with NOD/ESET you will need to create an exception for the above mentioned TAGS folder. SQLyog communicates *heavily* with the databases in that folder and NOD/ESET wants to triple-check every byte it seems!

Viewing 1 post (of 1 total)