@Rayman you just declared a function with multiple (11 I think) return values. If it worked, then it's a feature If it didn't work, then I missed an error case. I can't remember what the limit is on number of return values is supposed to be.
I'm trying hard not to tell you about any potential Fastspin issues I find until I hear you're home and all caught up.
They usually turn out to be my own fault anyway these days...
But, I know I'll forget if I don't mention this now...
This section of code goes off the rails if I don't use "x" instead of long[p][..]
It does work if I compile with a "-O0" option.
So, I think it's some kind of optimization thing...
'Check limits
x:=long[p][14] 'Something strange here! If I don't use x and use long[][] below it doesn't work!!!
if n > x'long[p][14]' 'in range?
n:=x'long[p][14]
x:= long[p][13]
if n < x'long[p][13] 'in range?
n:=x'long[p][13]
Just wanted to apologize to everyone for being MIA, but my brain is still recovering from a pretty serious illness and I'm under orders not to work for a few weeks Looking at screens gives me a headache anyway . The eventual prognosis is promising but I think its wise to listen to my doctor, so I won't be able to contribute much for a little while longer.
Just wanted to apologize to everyone for being MIA, but my brain is still recovering from a pretty serious illness and I'm under orders not to work for a few weeks Looking at screens gives me a headache anyway . The eventual prognosis is promising but I think its wise to listen to my doctor, so I won't be able to contribute much for a little while longer.
I'm glad to hear you're recovering. Take whatever time you need and don't feel obligated to respond to any messages here until it's safe for you to do so. We hope to see you back when you are well.
Just wanted to apologize to everyone for being MIA, but my brain is still recovering from a pretty serious illness and I'm under orders not to work for a few weeks Looking at screens gives me a headache anyway . The eventual prognosis is promising but I think its wise to listen to my doctor, so I won't be able to contribute much for a little while longer.
Absolutely listen to the doctor. Great to hear you are on the road to recovery. You have already contributed more than a lot of us, so relax and take care of your health.
flexgui/fastspin have been a huge part of getting up & running on P2... No need for apologizing for taking a break for your health. Best wishes Eric & get well soon!
You've gone above and beyond with FlexGUI and all the languages FastSpin supports, plus self-hosted Python.
Listen to your doc and take all the time you need to recover. You have definitely earned it!
... but my brain is still recovering from a pretty serious illness and I'm under orders not to work for a few weeks Looking at screens gives me a headache anyway . The eventual prognosis is promising but I think its wise to listen to my doctor, so I won't be able to contribute much for a little while longer.
Yes, after a brain injury, a long rest is best from what I've heard. I've a got neighbour now regretting quickly getting back on his mountain bike against doctor's orders.
... but my brain is still recovering from a pretty serious illness and I'm under orders not to work for a few weeks Looking at screens gives me a headache anyway . The eventual prognosis is promising but I think its wise to listen to my doctor, so I won't be able to contribute much for a little while longer.
Yes, after a brain injury, a long rest is best from what I've heard. I've a got neighbour now regretting quickly getting back on his mountain bike against doctor's orders.
Never could understand the reasoning behind paying for an expert opinion and then ignoring it. I have an older brother in law that does that regularly.
An interesting discovery I just made: the FlexGUI viewport supports ANSI / VT100 control codes. So far, changing foreground and background colors, bold, underline, as well as cursor positioning, viewports, etc all work.
Is this another @ersmith easter-egg, or was this generally well-known?
If there is any interest, I'll post the codes that work once I've reached my way to the bottom of the possibilities.
This "discovery" (humor me) makes debugging some things a bit easier for me. The perfect example is GPS data. I was getting clobbered trying to display the various values from a fast stream. Now I can make a debug screen that doesn't scroll when it updates, and use colors to flag values that are changing, out of range, or misbehaving.
With some terminals you even can get graphics.
I was too lazy for using more than black and green but more colours would have been possible.
Ask Marjory about "SIXEL".
Slowly (very slowly) starting to get back to work. If you can compile fastspin from source, please give it a try; there are a number of bug fixes, including some contributed by @"Roy Eltham" and @avsa242 . There's also a binary of the 4.1.4 beta on my Patreon page. I hope to have a "real" release later this week. It won't be as complete as I had wished, but it will be a definite improvement over 4.1.3.
Glad you're back! There's something I've been meaning to tell you about...
Somehow braces are not overridden by comments (single quote) (I think this is the problem).
I get strange errors if delete bottom of commented out brace, but not the top:
PRI HandleMouseUpForm1(p)|i 'app specific stuff
if (p==@Form1Option1) or (p==@Form1Option2)
i:=GetOptionValue(@Form1Option1) 'Rising Edge?
if i==1
dig.SetEdgeMode(0) 'rising edge
else
dig.SetEdgeMode(1) 'Falling edge
SetAnalogTrigger() 'change trigger settings
'{
'need to restart acquistion
asm
cogatn #(1<<digCog)
endasm
'} Something to tell Eric Smith about... Removing this line breaks Fastspin. Gives bizare error in USB code
EDIT: This is obviously about building flexgui as a whole which includes fastspin/spin2cpp/loadp2/PropLoader... The spin2cpp project itself builds without issue.
On macOS, I'm now getting an error when flexgui tries to build and link proploader... This happens on my Mac as well as the TeamCity build server that David Zemon had set up on my old iMac server. On my Mac I was able to get the build to complete by building proploader before running make within the top "flexgui" directory. The build states "o64-clang++ command not found", so I think the Makefile may be at fault.
Here's the log from the TeamCity build server:
/Users/myUser/Documents/buildAgent/work/497917564a46784a/proploader-macosx-build/bin/split /Users/myUser/Documents/buildAgent/work/497917564a46784a/proploader-macosx-build/obj/IP_Loader.binary /Users/myUser/Documents/buildAgent/work/497917564a46784a/proploader-macosx-build/obj/IP_Loader.h
16:07:50
o64-clang++ -Wall -DVERSION=\""v1.0-45 (2020-03-29 09:07:50 gb900b3c)"\" -DMACOSX -I/Users/myUser/Documents/buildAgent/work/497917564a46784a/proploader-macosx-build/obj -c src/main.cpp -o /Users/myUser/Documents/buildAgent/work/497917564a46784a/proploader-macosx-build/obj/main.o
16:07:50
/bin/sh: o64-clang++: command not found
16:07:50
make[1]: *** [/Users/myUser/Documents/buildAgent/work/497917564a46784a/proploader-macosx-build/obj/main.o] Error 127
16:07:50
make: *** [proploader-macosx-build/bin/proploader] Error 2
16:07:50
Process exited with code 2
16:07:50
Process exited with code 2 (Step: Build (GNU Make))
16:07:50
Step Build (GNU Make) failed
16:07:50
Publishing internal artifacts
Comments
Get well soon!
Jim
Hope you're still getting better!
I'm holding back on error reports.
But, this one is more of a user error report...
I did this by accident:
Obviously, the ":" should be a "|".
The compiler appears to have not expected such a bad mistake
Does Spin2 even need to differentiate between local variables and return variables?
Why not just let the first 8 or so be always returned and the rest not...
That is an interesting idea. It might simplify things.
I'm trying hard not to tell you about any potential Fastspin issues I find until I hear you're home and all caught up.
They usually turn out to be my own fault anyway these days...
But, I know I'll forget if I don't mention this now...
This section of code goes off the rails if I don't use "x" instead of long[p][..]
It does work if I compile with a "-O0" option.
So, I think it's some kind of optimization thing...
'Check limits x:=long[p][14] 'Something strange here! If I don't use x and use long[][] below it doesn't work!!! if n > x'long[p][14]' 'in range? n:=x'long[p][14] x:= long[p][13] if n < x'long[p][13] 'in range? n:=x'long[p][13]Absolutely listen to the doctor. Great to hear you are on the road to recovery. You have already contributed more than a lot of us, so relax and take care of your health.
Get well soon!
dgately
Listen to your doc and take all the time you need to recover. You have definitely earned it!
Take it easy and take the time to recover fully
Ditto what others have said.
Never could understand the reasoning behind paying for an expert opinion and then ignoring it. I have an older brother in law that does that regularly.
I think I might even like it better...
repeat io.sprintf(@buffer,@format,123.56,67) ser.str(@buffer) ser.tx(13) ser.tx(".") waitcnt(cnt+clkfreq) dat format byte "%8.1f = 0x%.3x",0 buffer byte " ",0 ' 20 should be enoughIs this another @ersmith easter-egg, or was this generally well-known?
If there is any interest, I'll post the codes that work once I've reached my way to the bottom of the possibilities.
It seems to support full VT100.
Enjoy!
Mike
This "discovery" (humor me) makes debugging some things a bit easier for me. The perfect example is GPS data. I was getting clobbered trying to display the various values from a fast stream. Now I can make a debug screen that doesn't scroll when it updates, and use colors to flag values that are changing, out of range, or misbehaving.
I was too lazy for using more than black and green but more colours would have been possible.
Ask Marjory about "SIXEL".
Regards,
Eric
Somehow braces are not overridden by comments (single quote) (I think this is the problem).
I get strange errors if delete bottom of commented out brace, but not the top:
PRI HandleMouseUpForm1(p)|i 'app specific stuff if (p==@Form1Option1) or (p==@Form1Option2) i:=GetOptionValue(@Form1Option1) 'Rising Edge? if i==1 dig.SetEdgeMode(0) 'rising edge else dig.SetEdgeMode(1) 'Falling edge SetAnalogTrigger() 'change trigger settings '{ 'need to restart acquistion asm cogatn #(1<<digCog) endasm '} Something to tell Eric Smith about... Removing this line breaks Fastspin. Gives bizare error in USB codeOn macOS, I'm now getting an error when flexgui tries to build and link proploader... This happens on my Mac as well as the TeamCity build server that David Zemon had set up on my old iMac server. On my Mac I was able to get the build to complete by building proploader before running make within the top "flexgui" directory. The build states "o64-clang++ command not found", so I think the Makefile may be at fault.
Here's the log from the TeamCity build server:
PropLoader's Makefile includes:
dgately