ID:2297703
 
Resolved
Filters did not work correctly and could cause a crash in some cases.
BYOND Version:512.1386
Operating System:Windows 10 Home 64-bit
Web Browser:Chrome 60.0.3112.113
Applies to:Dream Daemon
Status: Resolved (512.1387)

This issue has been resolved.
Descriptive Problem Summary:
atom/proc/Highlight(apply)
if(apply)
filters = filter(type="outline", size=1, color=rgb(255,0,0))
else
filters = null


This as well doesn't work.

src.filters = filter(type="outline")


When trying to use filters, using filter() at all will cause the project to not appear or even run when ran.

Expected Results:
Compile and apply the filter.


Actual Results:
Compiles and you can try and run it but no window appears and nothing in task manager shows.


When does the problem NOT occur?
When using just "filters = null"
Moved. Please be sure to post all beta bugs in this forum and with the full build number.
Kozuma3 wrote:
Descriptive Problem Summary:
atom/proc/Highlight(apply)
> if(apply)
> filters = filter(type="outline", size=1, color=rgb(255,0,0))
> else
> filters = null


This as well doesn't work.

src.filters = filter(type="outline")


When trying to use filters, using filter() at all will cause the project to not appear or even run when ran.

Expected Results:
Compile and apply the filter.


Actual Results:
Compiles and you can try and run it but no window appears and nothing in task manager shows.


When does the problem NOT occur?
When using just "filters = null"

I have the same.
https://puu.sh/xILWH.gif


I'll look into this right away. I wonder if something that worked in debug mode failed in release mode.
Lummox JR resolved issue with message:
Filters did not work correctly and could cause a crash in some cases.
I found the issue. A last-minute change I had to make to appease the Linux compiler was the cause of the problem; a copy-paste of a block clear resulted in clearing a local stack value instead of the actual filter memory.

Login to reply.