PropellerIDE 0.30.1 scrambled font issue
courtens
Posts: 101
I am so very glad to see PropellerIDE -- and the user friendly search function it finally provides. Too bad the tags Ctrl-1, Ctrl-2, Ctrl-3 ... and Alt-mouse-drag are not working like they did before. Also, I really wish there was a split-window (top/bottom) function.
Now, to my issues:
1) I am heavily relying on strings inside a TV-UI with symbols like the "pipe" and the "dot" from the Parallax font library. Now things got all scrambled. Is that Parallax font no longer supported?
Any idea what could cause this?
2) Unfortunately, I did not make a backup of my large file; and all my code is now messed up with characters like this "£â£â£" -- when going back to the old Propeller Tool. The drawing in my notes turned into gibberish.
Can this be undone?
I was excepting PropellerIDE to be more cross compatible with the old Propeller Tool.
Now, to my issues:
1) I am heavily relying on strings inside a TV-UI with symbols like the "pipe" and the "dot" from the Parallax font library. Now things got all scrambled. Is that Parallax font no longer supported?
Any idea what could cause this?
2) Unfortunately, I did not make a backup of my large file; and all my code is now messed up with characters like this "£â£â£" -- when going back to the old Propeller Tool. The drawing in my notes turned into gibberish.
Can this be undone?
I was excepting PropellerIDE to be more cross compatible with the old Propeller Tool.
Comments
1) The madness of unicode and it's various encodings.
2) The daft idea of putting schematics into source code
3) The fact that the Spin language is not specified anywhere.
4) Not using a source code management system like git
5) Not having backups of any kind.
Could you post your "corrupted" file here so we can see what has happened to it? Preferably ZIP it first so no further damage happens along the way.
It sounds like it has been converted to some encoding that the Prop Tool does not understand but is otherwise fine. I suspect the damage can be undone.
Sorry ... no easy way to pull sample files. But this should illustrate what I am seeing:
using Propeller Tool before
 phsa:=0 P6 d16 ┌┐ ─┘└─────────────────────────────opening in PropellerIDE and saving file -- arrow before phsa is an empty box (I found a substitute to simulate what in this HTML based representation; but the box is empty, not full as shown)‣ phsa:=0 P6 d16 ┌┐ ─┘└─────────────────────────────opening saved file now back in Propeller Tool gives me this phsa:=0 P6 d16 ┌┐ ─┘└───────────────────────────── ‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣‣What do you mean "no easy way"? You have the file, you have it in an OS, I presume you have a way to zip and post it.
thanks for the help
I think I just fixed it by swapping font in the editor to Parallax
To my mind developing software should not depend on having a particular font installed and used. Others will disagree of course.
This worked. Too bad I had to go reselect the font after closing PropellerIDE. Somehow PropellerIDE did not save my setting.
Or am I missing a point here? Anyone know?
Certainly, any system that uses a custom Font, should save that font when set !
just to clarify
["2) Unfortunately, I did not make a backup of my large file; and all my code is now messed up with characters like this "£â€£â€£" -- when going back to the old Propeller Tool. The drawing in my notes turned into gibberish.
Can this be undone?"]
The file still compiles ok ? - it is just the display rendering (aka font) that was at issue here ?
The idea itself is not daft, and I use
http://www.tech-chat.de/ascii-circuits.html
to include schematics.
Note. that does not use custom fonts - any monospaced font is ok.
Realizing that it is suffering from line wrap I tried to copy and paste it to an editor, no can do.
Admittedly I have used ASCII schematics for very simple things from time to time.
I retired the idea of going back to using Propeller Tool's, so the font issue is no longer a problem for me. Yes. The characters (space), (pipe) │, and (dot) did at first not work - but after changing the ProgellerIDE to using the Parallax font it somehow is OK... It may have done something to the file after saving it again.
My newest problem I am having using PropellerIDE is that I do not have the a visual help in the form of vertical lines. If I remember right, Spin allows up to 7 loop deep nesting code. Without these lines it makes it very difficult to code if one has a lot of notes inside the code. Some simple lines in the background like Notepad++ offers would help.
Sure. Works fine here, pastes into Notepad++ ?
OK, pastes fine into Sublime Text, looks quite good.
The issue was that I only see 14 lines at a the time in box on the page you linked. So it has to be copy and pasted a bit at a time which is hard work and error prone.
Looks quite good but I'm still not into the idea of schematics in source code.
@evanh, Bites lip, holds breath. Must not be taunted.