Practical debugging - Гісторыя версій

Cpasbanal: /* Debugging Toolips CSS/Layout */

2020-10-26T20:28:07Z

Debugging Toolips CSS/Layout

← Папярэдн. версія		Версія ад 22:28, 26 кастрычніка 2020
Радок 114:		Радок 114:
	=== Debugging Toolips CSS/Layout ===		=== Debugging Toolips CSS/Layout ===

	To inspect tooltip you need to pin it so it does not ~~dissapear~~.		To inspect tooltip you need to pin it so it does not disappear.
	Best way to do that is to inspect element which you have tooltip for, and in dev tools (or similar) force state to hover, i.e. select ":hov" icon and select :hover checkbox.		Best way to do that is to inspect element which you have tooltip for, and in dev tools (or similar) force state to hover, i.e. select ":hov" icon and select :hover checkbox.

Victoria La: /* Debugging my HTML/CSS layout */

2020-10-14T00:48:56Z

Debugging my HTML/CSS layout

@@ Радок 100: / Радок 100: @@
 * Using the "magnifying glass", you can click on any part of your game interface and check its HTML code and associated CSS styles.
 * You can even modify directly some CSS properties and see how it looks immediately in the game interface.
 === Debugging Toolips CSS/Layout ===

Victoria La: /* Debugging Toolips CSS/Layout */

2020-09-30T22:42:01Z

Debugging Toolips CSS/Layout

← Папярэдн. версія		Версія ад 00:42, 1 кастрычніка 2020
Радок 105:		Радок 105:
	Best way to do that is to inspect element which you have tooltip for, and in dev tools (or similar) force state to hover, i.e. select ":hov" icon and select :hover checkbox.		Best way to do that is to inspect element which you have tooltip for, and in dev tools (or similar) force state to hover, i.e. select ":hov" icon and select :hover checkbox.

			If this does not work: open the console (dev tools) large enough window, hover to make the tooltip appear and alt + tab to focus the console that will cover the tooltip. That way the onmouseout will never be triggered.

	=== Debugging my Javascript game interface logic ===		=== Debugging my Javascript game interface logic ===

Victoria La: /* Debugging my HTML/CSS layout */

2020-09-30T02:54:18Z

Debugging my HTML/CSS layout

← Папярэдн. версія		Версія ад 04:54, 30 верасня 2020
Радок 100:		Радок 100:
	* Using the "magnifying glass", you can click on any part of your game interface and check its HTML code and associated CSS styles.		* Using the "magnifying glass", you can click on any part of your game interface and check its HTML code and associated CSS styles.
	* You can even modify directly some CSS properties and see how it looks immediately in the game interface.		* You can even modify directly some CSS properties and see how it looks immediately in the game interface.
			=== Debugging Toolips CSS/Layout ===

			To inspect tooltip you need to pin it so it does not dissapear.
			Best way to do that is to inspect element which you have tooltip for, and in dev tools (or similar) force state to hover, i.e. select ":hov" icon and select :hover checkbox.


	=== Debugging my Javascript game interface logic ===		=== Debugging my Javascript game interface logic ===

Victoria La: /* Add traces to your code */

2020-09-30T02:49:13Z

Add traces to your code

← Папярэдн. версія		Версія ад 04:49, 30 верасня 2020
Радок 73:		Радок 73:
	Only the error log level will appear in production. This level should be used only for critical problems.		Only the error log level will appear in production. This level should be used only for critical problems.
	Other levels will show only in the development environment and can be used as you see fit.		Other levels will show only in the development environment and can be used as you see fit.

			Note: tracing likely won't work in constructor and game setup, use other methods (such as dumping on stdout)

	== Debugging my HTML/CSS layout ==		== Debugging my HTML/CSS layout ==

Volker78: Description was wrong/not working

2020-08-16T11:15:05Z

Description was wrong/not working

← Папярэдн. версія		Версія ад 13:15, 16 жніўня 2020
Радок 179:		Радок 179:
	* change instances of 2308257, and 2308258 to you own BGA Studio logins YourLogin0 and YourLogin1		* change instances of 2308257, and 2308258 to you own BGA Studio logins YourLogin0 and YourLogin1
	* change $id0 and $id1 to the player_ids from the table you want to debug, and have recently imported.		* change $id0 and $id1 to the player_ids from the table you want to debug, and have recently imported.
			* Before you load Slot1, open a second tab with the table, because after loading the slot, that tab will be unusable. In the second tab you can call LoadDebug() in the chat window

	<pre>		<pre>

Quietmint: /* Get the database matching a bug report */

2020-07-12T05:30:55Z

Get the database matching a bug report

← Папярэдн. версія		Версія ад 07:30, 12 ліпеня 2020
Радок 152:		Радок 152:

	== Get the database matching a bug report ==		== Get the database matching a bug report ==

			For a way to automate the below steps, see this post: https://boardgamearena.com/forum/viewtopic.php?f=12&t=16454#p63167

			---

	When a player creates a bug report in production, a snapshot of the game database is taken. You can get access to this snapshot from the studio by following the steps below:		When a player creates a bug report in production, a snapshot of the game database is taken. You can get access to this snapshot from the studio by following the steps below:

Tutchek: Added navigation

2020-04-15T21:16:07Z

Added navigation

← Папярэдн. версія		Версія ад 23:16, 15 красавіка 2020
Радок 1:		Радок 1:
			{{Studio_Framework_Navigation}}

	This page gives you practical tips to debug your game during development. Don't hesitate to share your difficulties with us so that we can improve this section.		This page gives you practical tips to debug your game during development. Don't hesitate to share your difficulties with us so that we can improve this section.

Een: /* Get the database matching a bug report */

2020-01-22T12:06:11Z

Get the database matching a bug report

← Папярэдн. версія		Версія ад 14:06, 22 студзеня 2020
Радок 157:		Радок 157:
	* In the "Errors in production" section, fill up the fields "Bug report ID" (this is the ID of the bug report in production) and "Studio table ID" (this is the ID of the table you created above) then click the "⇨ Load bug report state into this table save slot #1" button.		* In the "Errors in production" section, fill up the fields "Bug report ID" (this is the ID of the bug report in production) and "Studio table ID" (this is the ID of the table you created above) then click the "⇨ Load bug report state into this table save slot #1" button.
	* If the snapshot is correctly retrieved, you see a "Done!" message.		* If the snapshot is correctly retrieved, you see a "Done!" message.
	** '''Important note:''' if you see a "Done!" message but the game database is unchanged, it's that the snapshot is unfortunately not available (most likely because the bug report was declared too long after the game ended and the database had already been garbage collected to reclaim space).
	* Go back to the tab with your studio table and click "Load 1".		* Go back to the tab with your studio table and click "Load 1".
	* The page refreshes automatically and is broken. This is normal, as the player ids from the snapshot are the player ids of the production, not those of the studio. We'll need to update them.		* The page refreshes automatically and is broken. This is normal, as the player ids from the snapshot are the player ids of the production, not those of the studio. We'll need to update them.
			** '''Important note:''' if you see a "Done!" message but clicking "Load 1" doesn't bring any change, it's that the snapshot is unfortunately not available (most likely because the bug report was declared too long after the game ended and the database had already been garbage collected to reclaim space).
	* Click on the "Go to game database" button		* Click on the "Go to game database" button
	* For each table using player_ids, you'll need to update the player_ids from the production to use the player_ids from the studio. You can see the player_ids from the table page before entering the game by hovering over the player names.		* For each table using player_ids, you'll need to update the player_ids from the production to use the player_ids from the studio. You can see the player_ids from the table page before entering the game by hovering over the player names.

Een: /* Get the database matching a bug report */

2020-01-22T12:04:18Z

Get the database matching a bug report

← Папярэдн. версія		Версія ад 14:04, 22 студзеня 2020
Радок 157:		Радок 157:
	* In the "Errors in production" section, fill up the fields "Bug report ID" (this is the ID of the bug report in production) and "Studio table ID" (this is the ID of the table you created above) then click the "⇨ Load bug report state into this table save slot #1" button.		* In the "Errors in production" section, fill up the fields "Bug report ID" (this is the ID of the bug report in production) and "Studio table ID" (this is the ID of the table you created above) then click the "⇨ Load bug report state into this table save slot #1" button.
	* If the snapshot is correctly retrieved, you see a "Done!" message.		* If the snapshot is correctly retrieved, you see a "Done!" message.
			** '''Important note:''' if you see a "Done!" message but the game database is unchanged, it's that the snapshot is unfortunately not available (most likely because the bug report was declared too long after the game ended and the database had already been garbage collected to reclaim space).
	* Go back to the tab with your studio table and click "Load 1".		* Go back to the tab with your studio table and click "Load 1".
	* The page refreshes automatically and is broken. This is normal, as the player ids from the snapshot are the player ids of the production, not those of the studio. We'll need to update them.		* The page refreshes automatically and is broken. This is normal, as the player ids from the snapshot are the player ids of the production, not those of the studio. We'll need to update them.