I foresee that could be problematic with the PICAXE manual 2 pdf.Well I never knew that !
That's a helpful tool, but to take it one stage further when pressing the "The detailed help and examples" button it's a shame it doesn't take you to the relevant section" in the manual rather than just taking you to the start of the manual.
What is your screen resolution?Another small issue, when having multiple editor windows open I would like to be able to see the name of the file in the caption of the window.
Actually it is already there but it shows the complete path which is too long to show the name also.
Hi Westie,I foresee that could be problematic with the PICAXE manual 2 pdf.
The PE's quick syntax checker would be limited to links into the version of the manual provided with the PE.
The PICAXE manuals have 'bookmarks' already.I'm not sure that will be a problem.
I regularly use PDF files which have 'live' index pages and bookmarks.
There must be a way for an external application, such as PE, to open a PDF at a specific indexed page.
good find nick12ab.The PICAXE manuals have 'bookmarks' already.
The Adobe Reader command line reference says that automatic jumping to pages or named references so if named references means the same thing as bookmarks then the manuals need no modification for jumping to the correct section of the manual.
Did someone say cartoon??? (just kidding ;-)How about something like this:
I like the idea of the image changing with each new revision.
A new thread would have been better, but why don't you just use parallel processing? Or use the timers.Maybe not the right thread to post this request, but if you don't ask, you don't get!
Parallel processing, multiple outputs?
From here, named destinations are not the same as bookmarks but it will be possible to add named destinations with whatever software Rev-Ed use to create their manuals.but using the BASIC command names as per the bookmark text opened the pdf but did not go to the page. For example:
http://www.picaxe.com/docs/picaxe_manual2.pdf#clearbit
or
http://www.picaxe.com/docs/picaxe_manual2.pdf#nameddest=clearbit
Not too late and all suggestions welcome. Even if things don't happen to make it into the initial release of PE6 they will still be borne in mind and considered for later addition.Hopefully still not too late !
I'd say that is close then! I'd like to volunteer as beta/alpha tester.Even if things don't happen to make it into the initial release of PE6
I wouldn't read too much into a 'throwaway line' that was meant to indicate we're always open to suggestions.I'd say that is close then! I'd like to volunteer as beta/alpha tester.Even if things don't happen to make it into the initial release of PE6
A solution at present might be something like -I'm using servopos commands on B.6 and B.7, while I'm varying the binary output to an decoder chip on pins B.0, B.1 and B.2. Can't use outpinsb without messing up servo timing
For b0 = 0 To 7
Gosub SetLsbToB0
Next
SetLsbToB0:
If bit0 = 1 Then : High B.0 : Else : Low B.0 : End If
If bit1 = 1 Then : High B.1 : Else : Low B.1 : End If
If bit2 = 1 Then : High B.2 : Else : Low B.2 : End If
Return
It's a glitch with the syntax colour highlighting. All commands after the #endrem will still work correctly and simulation still works.I have, I think, found a small glitch. In my program I use capitals for all commands. This makes it much more readable. I recently discovered that I could use the directive #REM but #ENDREM isn't recognized. I had to use #endrem. Is this correct or do I have to use all directives with small characters?
From post #74, back in January 2012.Thanks for all the suggestions and feedback, we're pleased to say most of these are already covered in PE6 - more information soon.
Yeah we want an update!From post #74, back in January 2012.
Is there any news yet ?
A similar system already exists - clicking in the margin of a line makes a 'breakpoint' (red rectangle) appear in the margin and pressing Ctrl+K makes a 'bookmark' (blue rectangle) appear in the margin. A breakpoint will pause the simulator at that particular line but a bookmark won't. Unfortunately I din't think either are saved so when the file is closed they are lost forever. However you can use the #rem and #endrem directives to comment out sections of code (which makes them green AND ignored by the compiler) and these do get saved.Sort of a "remove before flight"-flag.