I'm not using the wireless but am using a 100Mb network cable.
Microsoft Windows Vista Home Premium 32-bit Mobile DualCore Intel Core 2 Duo T5750, 2000 MHz (12 x 167) With my notebook looks like I have to go back to version 0.25.0 which is a bit sad because I have donated and love the program and would like to use the latest version for people who donated. When the program freezes the log just stops.Īlso it doesn't matter is I'm downloading a large or small files. This is not just for hermes, which was included in RN 0.60.1, because I'm also having trouble with the. In Android using RN 0.60.0 or above FlatList is always blank and sometimes freezes the app even though I can see my data is coming in correctly in the console. The log file doesn't shed any light on the problem. Anything below 0.60.0 is fine on both platforms, and anything is fine on IOS. I can't go back any feather because when I click on the download link in the forum I get the error: Nice try. I would like to iterate through all objects in the dwg (that are displayed), select by linetype, and freeze (or not display) objects with that line type. The thing I'm going to try tonight is run 0.28.5 on a different computer but this is only for test because I would like to use my notebook to download with because it cheaper to run all night than my beast of a desktop computer. When I open up the app a blank screen appears and it freezes. I have gone back to version 0.28.5 and it does the same.
#XLIST BLANK FREEZES FULL#
It will lock both CPUs to full speed as well. What happens is Altbinz will freeze it doesn't matter if you have minimized it to the task bar or leave it open and maximized. I have on peak and off peak usage and download most of my stuff at night. The xml file is text so comparing a good xml file against a bad xml using a tool like Beyond Compare will help. I suspect you are not getting any results. Check the xList to see if it contains any data. I was running Altbinz 0.25.0 for a few months without a problem. Andrew Morton at 19:38 Using a different library is not going to fix the issue if the root cause is the data inside the xml file.
0 kommentar(er)
