ID 443488 - Relative file pathing does not function correctly within Nuke 12.2 if not using ./ within the filepath.

Problem summary
When using relative file pathing, you have two methods within the Read node to interpret the file location.

The first method is to use './' before the file to indicate the location
./test.exr

The second method is to directly use the file location, minus the './'.
test.exr

Within the Nuke 12.2 release, the second method incorrectly amends a ':' colon to the start of the filepath and corrupts the file pathing
​

​

Note: This only occurs in the Nuke 12.2 release.

Customer reported version
nuke.12.2v1

Customer reported platform
windows10

Steps to reproduce

1) Open a new Nuke 12.2 session

2) Within the Project Settings, set the relative path to the script's location by clicking 'Script Directory'.
​

​

3) Read in footage

4) Save the script to the same location as this footage. (to create the relative path link)

5) Remove the directory from within the Read nodes file path, leaving just the filename and extension itself.
​

​

Result: Error occurs

6) Reproduce steps 2-5 in Nuke 12.1 and earlier releases
Result: No error

Expected behaviour
When the relative pathing is setup, you should be able to use either of the two methods within the Read node

Actual behaviour
Without the './' amended to the file path relative pathing does not work in Nuke 12.2

Workaround
Use the first method, including the './' within the Read nodes file path when relative pathing in Nuke 12.2.

Reproduced by support
This bug has been reproduced in:
Nuke 12.2v1 - Windows 10, Centos 7, MacOS 10.14.6

Unable to reproduce bug in:
Nuke 12.1v4 - Windows 10, Centos 7, MacOS 10.14.6

Earliest version tested
Nuke 12.1v4
- This issue doesn't appear in this version and has regressed