I'm having a constant issue of particle effects not appearing in the editor. Everything works fine when I first create them, but after some time they stop appearing. I just see the black background, but the particles aren't there.
The only way I'm able to deal with this problem is to delete the node and create a new particle node with the same attributes, which is time consuming and annoying. And then, after a while, the same thing happens to the new particle nodes.
Anyone else experience this?
This happens to me all of time after editing a value and switching to code view of another page. Come back and the preview is gone. Can confirm it is still broken in Xcode 7.3 Beta
There are a couple of home remedies that work until it gets fixed by Apple.
Right click on the file --> Open As --> Quick Look
select a different file and come back and it should work now
or
Close the emitter document with File --> Close “Particle.sks” (Control-Command-W) and reopening it should circumvent the issue.
Hope this helps in the mean time
Related
I'm working on the code in a project when I suddenly notice the ViewController in Storyboards is greyed out with the name of the VC in the center.
Here's a screenshot..
I was only editing some code on the right and I'm not sure exactly when, but my eyes adjusted and noticed this VC completely greyed out in Storyboards.
I tried deleting Derived Data, cleaning, quitting Xcode, building again, etc.
Nothing seems to work... ANy help with this would be super appreciated. I'm also very new to programming in general.
Well it turns out if you ever run into this problem, it's because you're not paying close attention and haven't realized you've somehow magically deleted your entire view inside the ViewController.
I did this once before by hitting something randomly on my keyboard (don't know what it was) but that time I saw it happen and just hit "undo".
This time I was passed the point of simply hitting "undo" and had to add a view again and rebuild and reconnect all the components in the view. That was basically it. Problem solved...
I am having a problem where my content is repeatedly being shifted to the right in the storyboard for multiple view controllers when I open the project. I have done nothing at this point, simply opened it. Further, undoing the modifications through git does nothing. I fix the problems and go about my day adding new features... the apps run fine in the phone and appear normal in the storyboard. However, when I open the project the next day, same thing happens and I have to fix everything again. Has anyone else experienced this issue, and what was your resolution to the problem?
I figured out what the problem was. On my first View Controller, I had some labels that had somehow become set to a width of zero. After I fixed them, and embedded them in a stack, the problem resolved itself. I have no idea how this screwed up several other view controllers; however, fingers crossed, the corruption hasn't happened again since I fixed it.
Well apparently there is just some display bug in Xcode. When I click on a new size class and click back, the elements are restored to their correct size. This was maddening, but apparently it's working fine now if I do this quick fix.
Is it just me, or does this happen to anyone else? Occasionally if I am coding inside of a huge class, the source code text begins to chop it's way out to a white screen as I scroll. However, when I vigorously scroll to the top, then back down again. The source code re-appears again.
What could be the issue? Is there a work around? This issue is so annoying!
Go to Preferences->General tab and uncheck "Show live issues" under Issues. Notice that this is a work around to be able to continue working with Xcode, at least until they issue an official fix. This glitch seems to be noticeable when you have lots of lines of code (1000+).
After this, the glitch will still be happening but not while coding but during building phase. Not perfect but at least you will be able to continue working.
So I have a really weird error at the moment. I'm just about ready to deploy my app to the App Store (having already had several debug versions running as expected on my iPhone), but all of a sudden, mouse clicks do not appear to work on one single frame.
They run as expected in Flash CS6 Pro's iPhone Simulator (ADL).
The events are set up in the same way across the few frames and there should not be an issue at all. I have not changed the event listeners or functions since updating other elements of program.
It is also worth noting that the animation for MOUSE_DOWN on these buttons is working correctly.
I have tried the following to fix the problem, but to no avail:
Add the event listeners directly to each button
Have one event listener handling every single button
Add that single event listener to the stage
Use the MOUSE_UP event instead of MouseEvent.CLICK
Prompt help would be greatly appreciated as I am hoping to deploy this app to have it reviewed ASAP. Also, simply because it is confusing the heck out of me..
Thanks a lot in advance,
Harry.
Having a second import for flash.events.MouseEvent caused a conflict which stopped mouse clicks from working (the import statement was called again on this specific frame, hence why other frames worked as expected but this one didn't).
I have a TTLauncherView in my ios app. I have allowed users to edit and move their items around, however it does not appear that you can move the item from one screen to another, does anyone know how to do this?
that's looks like another a bug in three20 library. I just checked an old app of mine and moving items from page to page works fine. It means it might be another iOS 5 issue.
You can open a bug for it in http://github.com/facebook/three20, hopefully someone will fix it.
If I'll get around to it, i'll check it and fix it. I have a few apps using it, so I might need to do that.
I experienced a similar problem. It seems to be a bug just for the first icon on that page (i.e. creating a new page) - adding just add another icon to that page works fine (at least for me).
You can get around this bug by dragging the icon to the new page and releasing it on the first row (on the top of the page!). This isn't really satisfying, but perhaps a good starting point.