Recent versions: ||| Galaxytool: v5.1 ||| Galaxytoolbar: v2.6.32 |||

Difference between revisions of "Toolbar compatibility"

From Galaxytool wiki
Jump to: navigation, search
m (robot Adding: es:Compatibilidad Toolbar)
(255)
Line 10: Line 10:
 
You must not disable the message button at the galaxyview. Otherwise you won't be able to update them using the toolbar.
 
You must not disable the message button at the galaxyview. Otherwise you won't be able to update them using the toolbar.
 
Currently you also have to disable the "view report" button.
 
Currently you also have to disable the "view report" button.
 +
 +
=== Neogame ===
 +
We recommend disabeling Neogame all together. In some configuarations it may help to enable reduced galaxyview. Since the new design of Ogame will most likely result in Neogame being redesigned or abandoned, there is no need for us to write a workaround for this old tool.
  
 
[[de:Toolbar Kompatibilität]]
 
[[de:Toolbar Kompatibilität]]
 
[[es:Compatibilidad Toolbar]]
 
[[es:Compatibilidad Toolbar]]

Revision as of 12:19, 18 November 2008

FoxGame

If you enable several buttons at the FoxGame extension you may experience problems during upload of data. ( like for example the extra buttons for the FoxGame database features )

Disable any buttons at the galaxyview, statistics, alliance overview and reports at your foxgame settings. To do this, go to foxgame settings and disable all radiobuttons at the "Databases" tab.

There is NO problem with the reduced galaxyview if you update the galaxytool only with the toolbar and not manually at the textarea of the galaxytool.

Ogame Commander

You must not disable the message button at the galaxyview. Otherwise you won't be able to update them using the toolbar. Currently you also have to disable the "view report" button.

Neogame

We recommend disabeling Neogame all together. In some configuarations it may help to enable reduced galaxyview. Since the new design of Ogame will most likely result in Neogame being redesigned or abandoned, there is no need for us to write a workaround for this old tool.