WordWrapOut()
. If you remove my #if 0
s in WordWrapOut()
, you'll notice some more strange behaviour.Everything works OK if you comment out line 242 in
NXTFileManager.nxc
:
Code: Select all
// FileTaskOpen(fname);
WordWrapOut()
. If you remove my #if 0
s in WordWrapOut()
, you'll notice some more strange behaviour.NXTFileManager.nxc
:
Code: Select all
// FileTaskOpen(fname);
I apologize for the delay. I will try to remember to upload a new test release tonight.schodet wrote: OK, but, I did not see the new image yet (here? http://bricxcc.sourceforge.net/test_releases/).
nbc -Z3
- NXTFileManager.rxe
gave a File Error! -5
when running the program, so I nexttool -clear
ed all the files off my NXT, and recompiled/downloaded the program. Now, if I press the right button, the program freezes and the display clears halfway. (The screen was refreshing while WordWrapOut()
executed and froze the NXT?)nbc -Z1
- It works fine - the program doesn't freeze/crash. At least, not while navigating through the file list.-Z3
. I don't know about -Z2
, though.)__strToLines_7qG2_szOut_7qG2_000
variable's value never changes during the program! It's always 0x0
.LCD_LINE4
text in WordWrapOut()
. (One of the #if 0
s.)There should not be any duplicate identifiers. Can you elaborate?muntoo wrote: EDIT: Also, the output NBC code has a lot of duplicate identifiers. You might wanna fix that.
EDIT 2: Attached shorter version (still a bit long) that still gives me trouble.
I've been feverishly trying to finish up a project that has delayed posting a new test firmware and compiler/IDE. I apologize for the delay. I will post here when I have uploaded a new test release zip with the firmware image and a compiler and test program.pbenco wrote:Dear afanofosc
I have a digital scope too, 200MHz capable, how could I help?
Could you provide a test firmware with the speedy i2c, and a test program able to expose the behaviour you try to catch.
Best regards
ben
No problemafanofosc_99 wrote:I've been feverishly trying to finish up a project that has delayed posting a new test firmware and compiler/IDE. I apologize for the delay. I will post here when I have uploaded a new test release zip with the firmware image and a compiler and test program.
I meant duplicate definitions like this:afanofosc_99 wrote:There should not be any duplicate identifiers. Can you elaborate?
Code: Select all
dseg segment
;------- definitions -------
// ...
Location_def struct
X sword
Y sword
Location_def ends
// ... Later ...
Location_def struct
X sword
Y sword
Location_def ends
// ...
dseg ends
Users browsing this forum: No registered users and 0 guests