Checks
Problem description
When double-clicking an event/code line listed in the "Find Results" or "Bookmarks" windows/bars, the browser will switch to the correct event sheet and highlight the selected event, but will no longer automatically scroll up or down in the sheet to the location of that event. Now you have to spend time scrolling around searching for the event you attempted to go to, defeating the navigational purpose of "Find" or "Bookmarks".
Upload a project
Car Selection Screen.zip
Steps to reproduce
- Open any project with enough events in one sheet that you can't see them all on one screen, such as the Car Selection Screen example.
- Press Ctrl+F and search for text in the sheet, such as "enter pressed" and then double-click the resulting entry, to attempt to navigate to it.
- Note that this will not automatically scroll to the result.
Observed result
Can't double-click a "find result" or "bookmarks" entry to snap to the selected event anymore.
Expected result
Could still double-click an entry to snap to the selected event.
Affected platforms
Windows
Affected browsers
Chrome, Firefox
Last unaffected release (including beta releases)
r487.3
First affected release (including beta releases)
r488
Additional remarks
I've noticed the notes for r488 mention "Event sheet view: don't scroll when selecting content", but to be clear, the issue I'm describing is not about just selecting by clicking a search result, (which never navigated to content before, if I remember correctly?) but instead about DOUBLE-clicking a search result. I understand why you don't want the editor to scroll to something you _single-_clicked, but double-clicking to easily navigate to content was the entire purpose of the "Find Results" and "Bookmarks" windows, and they were extremely important features, just like the Ctrl+F search features in any other code editor or various other programs have.
If breaking this usability was an intentional change as the patch note seems to imply, please, please reconsider. I would never have guessed this was an intended change rather than just a bug, and the r488 summary doesn't list a specific reason this was done so I am at a loss.
Platform information
Product: Construct 3 r488 (beta)
Browser: Firefox 151.0
Browser engine: Gecko
Context: browser
Operating system: Windows 10
Device type: desktop
Device pixel ratio: 1
Logical CPU cores: 6
Approx. device memory: (unavailable)
User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:151.0) Gecko/20100101 Firefox/151.0
Language setting: en-US
Audio sample rate: 44100 Hz
Audio output channels: 2
Audio output interpretation: speakers
Renderer: WebGPU
Compatibility mode: no
Supports GPU profiling: yes
Major performance caveat: no
Maximum texture size: 16384
Adapter details: unknown/unknown
Adapter features: bgra8unorm-storage, core-features-and-limits, depth-clip-control, depth32float-stencil8, float32-filterable, indirect-first-instance, rg11b10ufloat-renderable, texture-compression-bc, texture-compression-bc-sliced-3d, timestamp-query
Checks
Problem description
When double-clicking an event/code line listed in the "Find Results" or "Bookmarks" windows/bars, the browser will switch to the correct event sheet and highlight the selected event, but will no longer automatically scroll up or down in the sheet to the location of that event. Now you have to spend time scrolling around searching for the event you attempted to go to, defeating the navigational purpose of "Find" or "Bookmarks".
Upload a project
Car Selection Screen.zip
Steps to reproduce
Observed result
Can't double-click a "find result" or "bookmarks" entry to snap to the selected event anymore.
Expected result
Could still double-click an entry to snap to the selected event.
Affected platforms
Windows
Affected browsers
Chrome, Firefox
Last unaffected release (including beta releases)
r487.3
First affected release (including beta releases)
r488
Additional remarks
I've noticed the notes for r488 mention "Event sheet view: don't scroll when selecting content", but to be clear, the issue I'm describing is not about just selecting by clicking a search result, (which never navigated to content before, if I remember correctly?) but instead about DOUBLE-clicking a search result. I understand why you don't want the editor to scroll to something you _single-_clicked, but double-clicking to easily navigate to content was the entire purpose of the "Find Results" and "Bookmarks" windows, and they were extremely important features, just like the Ctrl+F search features in any other code editor or various other programs have.
If breaking this usability was an intentional change as the patch note seems to imply, please, please reconsider. I would never have guessed this was an intended change rather than just a bug, and the r488 summary doesn't list a specific reason this was done so I am at a loss.
Platform information
Product: Construct 3 r488 (beta)
Browser: Firefox 151.0
Browser engine: Gecko
Context: browser
Operating system: Windows 10
Device type: desktop
Device pixel ratio: 1
Logical CPU cores: 6
Approx. device memory: (unavailable)
User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:151.0) Gecko/20100101 Firefox/151.0
Language setting: en-US
Audio sample rate: 44100 Hz
Audio output channels: 2
Audio output interpretation: speakers
Renderer: WebGPU
Compatibility mode: no
Supports GPU profiling: yes
Major performance caveat: no
Maximum texture size: 16384
Adapter details: unknown/unknown
Adapter features: bgra8unorm-storage, core-features-and-limits, depth-clip-control, depth32float-stencil8, float32-filterable, indirect-first-instance, rg11b10ufloat-renderable, texture-compression-bc, texture-compression-bc-sliced-3d, timestamp-query