Rémi Verschelde 9ad9d1f3b3 Don't localize paths that contain but are not in the resource path ...

This issue could be triggered if you try to access a path which contains
the resource path string in its absolute path, while pointing to a directory
which is *not* in the resource path.

It's clearer with an example: with `/my/project` as resource path, the
previous logic would also localize `/my/project_data` to `res://data`, which
is incorrect and would lead to a cryptic error.

Fixes #24761.

Co-authored-by: volzhs <volzhs@gmail.com>

2019-05-30 16:03:12 +02:00

37 KiB

Raw Blame History

View Raw