adireddy / eclihx

Automatically exported from code.google.com/p/eclihx
0 stars 0 forks source link

Problems View #67

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. do some error on code
2. compile it

What is the expected output? What do you see instead?
I expected the error will show in problems view, but there is nothing, but in 
the console there are the errors, but we can do quick click and go to the line 
of the error

What version of the product are you using? On what operating system?
I'm in mac

Please provide any additional information below.

Original issue reported on code.google.com by alijayameilio on 3 Mar 2011 at 11:37

GoogleCodeExporter commented 9 years ago
Please, could you provide a less possible example of haxe code with such 
behaviour and copy the console output here?

Original comment by goodwi...@gmail.com on 3 Mar 2011 at 2:56

GoogleCodeExporter commented 9 years ago
Hmmm... may I ask something :-?
has the "Problems View" been implemented?
So the errors are not just in "Console View" but in "Problems View" too...

Original comment by alijayameilio on 5 Mar 2011 at 4:15

GoogleCodeExporter commented 9 years ago
Yep, it has been implemented and I have tested it on Windows and on Ubuntu. 
That's why I'm asking you to give a simple example where your problem appear. I 
will try to understand is that Mac specific or not.

Original comment by goodwi...@gmail.com on 5 Mar 2011 at 9:13

GoogleCodeExporter commented 9 years ago
hmmm... i have the screenshoot for you :D
https://picasaweb.google.com/lh/photo/G7hB5mzEn3JakDSm7UX_-Q?feat=directlink

Original comment by alijayameilio on 6 Mar 2011 at 4:54

GoogleCodeExporter commented 9 years ago
Interesting. I really can't reproduce it, under the same conditions I can see 
two errors in the Error View. So could you run haxe with the hxml file from the 
console and redirect the error output to the file and attach it to this issue? 
I expect that there's some platform dependent encoding problem or problem with 
new line character which lead to errors in the parsing (see 
http://code.google.com/p/eclihx/source/browse/eclihx.core/src/eclihx/core/haxe/i
nternal/HaxeOutputErrorsParser.java if you're familiar with java).

I will prepare version with extended logging if your output file don't help to 
understand the reason of the bug.

Original comment by goodwi...@gmail.com on 6 Mar 2011 at 1:43

GoogleCodeExporter commented 9 years ago
hmmm.... what do you mean about redirect the error output to the file? how?

Original comment by alijayameilio on 6 Mar 2011 at 3:05

GoogleCodeExporter commented 9 years ago
I think I have fixed it. Please check in trunk version from the 
http://download.eclihx.org/eclihx/updatesite/trunk/ eclipse update site.

I will be appreciate to you if you post here did it help.

Original comment by goodwi...@gmail.com on 7 Mar 2011 at 2:58

GoogleCodeExporter commented 9 years ago
excuse me :-?
can you show me step by step to fixed it :-?
i just don't understand...
i'm a little bit new in eclipse environment

Original comment by alijayameilio on 8 Mar 2011 at 9:40

GoogleCodeExporter commented 9 years ago
Oh, sorry. Please proceed with the http://www.eclihx.org/installation-notes, 
but instead adding the stable update site written there, add 
http://download.eclihx.org/eclihx/updatesite/trunk/ url. You will need to 
uncheck "groups items by category" in the Install dialog and after that you'll 
see two features. Check the EclihX Feature (not the tests) and click next. 
After that Eclipse will warn you that it will do update instead new 
installation and with several more next and restart of the eclipse it will be 
done. 

Original comment by goodwi...@gmail.com on 8 Mar 2011 at 10:38

GoogleCodeExporter commented 9 years ago

Original comment by goodwi...@gmail.com on 8 Mar 2011 at 10:39

GoogleCodeExporter commented 9 years ago
nice :D... running smoothly :D thanks :D

Original comment by alijayameilio on 8 Mar 2011 at 10:51

GoogleCodeExporter commented 9 years ago
Good! Many thanks for posting this nasty bug and for help in resolving.

Original comment by goodwi...@gmail.com on 8 Mar 2011 at 1:11