I know it can be frustrating when something doesn't work like you want it to, but really the best way for us to help you is for you to post an example. I know with my own extensions that it is impossible for me to track down a bug unless I can reproduce it. The only way your going to get the bug fixed is to provide an example where it crashes.
The key to isolating the fault is to think ahead and analyze the whole thing as much as conceivable. You need to forsee, to the best of your ability, everything that can possibly go wrong.Debugging will always be a tedious but necessary task and there is no simple way of doing it if you expect to catch all the bugs. Then again, we've come a long way from the days a "bug" literally meant a moth in the vacuum tube.....
I'll see if I can reconstruct the bug for you guys... I ended up deleting the iconlist and using the humble dropdown list.. <img src="/center/images/graemlins/wink.gif" alt="" />
-Mel
[]The bad news is that I can't post the example. my company won't allow me to. In the object's defence, I have it doing the exact same thing in another app and it works fine. (but there are no frame navigations in that app!)[/]
MelliGeorgiou's the reason why we are asking for an example is to learn from your code. Frankly your description of the bug is very vague and of little help to anybody trying to help you fix it.
Generally, I recommend anybody reporting a bug mention MMF Version (ie Developer R421), Second you need to describe the operating system your using, along with what revision level. Thirdly you need to mention memory and hardware configurations.
Next when your reporting a crash you need to look carefully at what the report is saying. Which module is actually crashing.
If want the rest of us to help you, make a cut down example, it should take you all of 15 minutes. If you've got graphics in it that you don't want copied, disfigure them or fill them in. Cut out code that is not necessary to show the bug.
Finally if you want this bug fixed you may need to send either Clickteam or both the developer of the extension a working example, that is adequately commented and hope they have the time to fix it for you.
I think I figured out where the issue is guys.. The object seems to not get along with MooClick..
When my server is on, and Moo has connected to it at the start of the frame, that is when all the issues begin. If my Mooclick server is not online, the iconlist object doesn't crash. (but the app doesn't work! lol)
I've done the cut down version of the client, I just need to do a quick cut down version of the server...
I'll post back in a bit..
-Mel
check out the cut down version here:
http://homepage.mac.com/melligeorgiou/IconListBug.rar
WORKFLOW:
First launch the small server app. Leave it in the background. Then launch the client app. (I've included both the app and the mfa of the cut-down client.)
With the server running, this is where the iconlist object is unstable. You can try to create an account or log in at this point.
try to log in as username: []admin@test.com[/] and Password: test ... If you can get that far without crashing.. Then turn off the server and try using just the client..
The client should now work without crashes... Which is confusing, because it makes you think that the iconlist object is conficting somehow with moo..
That's where my analysis of the situation ends I'm afraid.
I hope you guys find the files useful to find the bugs..
oh yeh, you can't turn the server off by clicking the close button. You have to go to Server>Exit Server.
-Mel
Posting Permissions
Reply With Quote