You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
headHave array shows up as red text. Trying to edit the 15th or 16 array and importing it back will cause the resulting .sol file to appear corrupted to the application. S7_SHARED.sol.zip
The text was updated successfully, but these errors were encountered:
I took a look at this in Firefox 115 and not sure i can replicate the issue. I opened the file and went to the headHave array. I didn't see anything in red text.
You said to try editing the 15th or 16th array, i assume you mean integer as in the children within the array? I edited the 15th item from a 0 to a 1 in the array and saved it.
I also re-saved the file prior to editing it and compared it to the original. Without editing, the file saved exactly the same as the original.
With the edit, the only difference was one byte (the value i changed).
At this point I don't see any reason why the application would think it's correct. If possible, please give me more details on how to replicate the issue. Step by step exactly would help. Thanks.
Chrome 120 with guest profile so it's a brand new browser profile every time it's launched.
Steps:
Use "Open" to open S7_Shared.sol
search for "headhave"
Expected:
I can expand the array and show its content
Actual:
Red text on array headHave and clicking the triangle shows nothing. secHead (I think that is called?) also behaves the same
Regarding the app data corruption, I strongly think that the app itself has a bug preventing that only array element to be set as 1 and not detect some sort of corruption. Editing other elements in the array does work and the app won't detect the edited SOL as corrupted.
headHave array shows up as red text. Trying to edit the 15th or 16 array and importing it back will cause the resulting .sol file to appear corrupted to the application.
S7_SHARED.sol.zip
The text was updated successfully, but these errors were encountered: