Empty Condition List

All closed bug reports are moved here.

Post » Mon Apr 03, 2017 2:53 pm

Steps to reproduce
1. Click add event on event sheet
2. This step is an example with the System event: Click System.
3. On the "Angles" section, click is between angles (specifically on it's icon that looks like a gear).
4. Cursor should be on top of the back arrow button icon. Click to go back to System's lists of conditions window.
5. Again but with quick successive clicks from System's list window to "Is between angles" window and back to System's lists window.
6. Start typing anything in the search bar while the lists is blank.

Observed result
A blank screen of no lists of conditions. Following a search cause a crash. Anything with clicking back and forth rapidly will not allow C3 to load it's lists of conditions. Going back or closing the create event window will reset the empty lists away.

Expected result
Should not have an empty list with fast clicks of going back. Should have a fail save trigger of some sort to tell if the user has already exited the condition window it just entered, so that the condition lists will re-appear. If not, a simple search will crash the engine.

I bump upon this bug when I'm trying to prototype something rapidly. So this issue might be worth the patch.

Error report information
Type: unhandled exception
File: https://editor.construct.net/r14/main.js, line 140, col 82262
Message: Uncaught TypeError: Cannot read property 'ǃt' of null
Stack: TypeError: Cannot read property 'ǃt' of null at ǃr.ǃd.ǃaP.ǃGml.ǃGwG (https://editor.construct.net/r14/main.js:140:82262) at HTMLInputElement.ǃ$L.addEventListener (https://editor.construct.net/r14/main.js:140:80106)
Construct 3 version: r14
URL: https://editor.construct.net/
Date: Mon Apr 03 2017 22:33:15 GMT+0800 (Malay Peninsula Standard Time)
Uptime: 172.7 s

Platform information
Browser: Chrome
Browser version: 57.0.2987.133
Browser engine: Blink
Browser architecture: 64-bit
Context: browser
Operating system: Windows
Operating system version: 10
Operating system architecture: 64-bit
Device type: desktop
Device pixel ratio: 1.25
Logical CPU cores: 8
User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36

WebGL information
Version string: WebGL 2.0 (OpenGL ES 3.0 Chromium)
Numeric version: 2
Supports NPOT textures: yes
Vendor: Google Inc.
Renderer: ANGLE (Intel(R) HD Graphics 4600 Direct3D11 vs_5_0 ps_5_0)
Major performance caveat: no
Maximum texture size: 16384
Point size range: 1 to 1024
Extensions: EXT_color_buffer_float, EXT_disjoint_timer_query_webgl2, EXT_texture_filter_anisotropic, OES_texture_float_linear, WEBGL_compressed_texture_s3tc, WEBGL_debug_renderer_info, WEBGL_debug_shaders, WEBGL_lose_context
Posts: 177
Reputation: 6,815

Post » Mon Apr 03, 2017 3:22 pm

Just in case your steps may be unclear, post a gif ;)


Key thing being being fast enough
Posts: 246
Reputation: 3,822

Post » Tue Apr 04, 2017 2:41 pm

Thanks, should be fixed in r16.
Scirra Founder
Posts: 24,910
Reputation: 198,648

Return to Closed Bugs

Who is online

Users browsing this forum: No registered users and 0 guests