Done with the problem faced of loosing screen.

[perminder-17]

Fixes #2483

Changes: I have make the preview screen where we cannot loose it. Please check the video.

p5.js.Web.Editor.5.mp4

I have done my best to change it.

I have verified that this pull request:

• has no linting errors (npm run lint)
• has no test errors (npm run test)
• is from a uniquely-named feature branch and is up to date with the develop branch.
• is descriptively named and links to an issue number, i.e. Fixes #123

[perminder-17]

U may check @lindapaiste whenever u are free.

[lindapaiste]

It looks like you're combining two approaches here. You are setting a maxSize state but not ever using it. Instead you're setting the maxSize of the SplitPane directly from the window.innerWidth.

The code that you have here will actually work, but in a way that is very roundabout. Resizing the window calls the resize event handler, which calls setMaxSize. That changes the state of the component and forces a re-render, so the props of the SplitPane will get re-evaluated using the current value of window.innerWidth.

To keep the code cleaner I recommend the following changes:

1. Remove window.innerWidth as a dependency of the useEffect. You only need to add the resize event listener once. The dependencies should be [] or [setMaxSize] (both will only evaluate the effect once). If that is confusing, consider that the handler could be written as const updateInnerWidth = (e) => { setMaxSize(e.target.innerWidth); };.
2. Assign the state to a variable maxSize and use this to control the SplitPane : maxSize={maxSize * 0.965}.
3. As I'm writing this, I realize the issue of having an undefined value the first render and now I suspect that you probably wrote it the way that you did to avoid getting an NaN value from multiplication with undefined. How about we set the initial value of the state from the window? const [maxSize, setMaxSize] = useState(window.innerWidth);

[perminder-17]

I sincerely apologize for the delay @lindapaiste . Upon reevaluating my approach, I have recognized the shortcomings and made the necessary adjustments as per your guidance. Thanks for your suggestion.

[raclim]

Thanks for working on this! I'm going to merge this in as it seems to resolve the issue for now. Please feel free to add any further comments or changes before the next release around next Tuesday, January 16.

[perminder-17]

Thanks for the merge @raclim and I will definetly add any further changes before 16th of Jan. Really thanks for considering me. :)