tr1p1ea wrote:For developing programs that dont need super accurate timings, dont use flash and dont have to use certain ports, VTI is ok.
When writing my first 83 game (Traz) as a TI newbie, I wanted to use direct LCD write commands to update only the changing parts, i. e. the ball and possibly the brick it just hit. However, I didn't know about the delay needed... It worked beautifully on VTI, but it garbled the screen on the real calc in a shape that reminded of the ball's trajectory. That was a nice 'bug' to hunt down. I ended up using _GRBUFCPY_V.
Lack of breakpoints is my problem, sorry (still in development). Brass will export breakpoint information, the current (rubbish) PTI front-end which comes with Latenite doesn't do anything with them.
The screenshot I posted of the new debugger front-end will (and does) support breakpoints. I need to add the on-screen keypad and variables watch window though.
Edit: Never mind
I was wondering if you could make it so that when you double click on a *.lnp file it will run LateNite, like opening a *.doc file by double clicking it
Please "encourage" me to work more on any way you deem necessary
Edit: Never mind
I was wondering if you could make it so that when you double click on a *.lnp file it will run LateNite, like opening a *.doc file by double clicking it
You have to manually link the file to the prog with windows.
1st way
1.go to folder options (file types)
2.add .lnp, and changed the icon
3.click on open with... (the change botton)
4.find LateNite...
5.select enter
for some reason, it always gives me wordpad as what it opens *.lnp files with
2nd way
1.go to folder options (file types)
2. add .lnp
3.click on advanced
4. change icon
5. add new action: open (or run)
6. set application to LateNite
This way always gives an error: could not open 'Z:\LateNite'
LateNite is located in 'Z:\Latenite Z80 Editor\', so this isn't correct
It also gives an object reference error, asking if I want to debug LateNite.
LateNite continues to open itself, but doesn't give you beginning menu (where you choose to create a new project or open an existing one)
Please "encourage" me to work more on any way you deem necessary
In the second attemt you described, try to put the path to Latenite in quotes. As in "Z:\Latenite Z80 Editor\Latenite.exe". That should solve the error I guess.
not sure, but the spaces in 'Z:\Latenite Z80 Editor\' might be causing problems. Try what Timendus said (double quotes and full path link), and if that doesn't work try renaming the folder.
Also, why not do what Ben said? much easier, unless you're on an older version of windows, in which case it might not behave the same way. good luck.
If WordPad still opens the file after you added it, right-click and select "Open With..." - it should list both WordPad and Latenite, assuming when you added it manually you added it correctly. Select Latenite and tick the box for "always open with this program".
I've really never known what the EarlyMorning problem really is - as far as I remember, EarlyMorning wouldn't run properly unless it was being run from it's own local directory - Latenite had a hack that modified the working directory first, and EM worked fine (at least, for me).
Too-rapid tooltips will probably have to wait until I've written a new text editor control, sorry. Breakpoints will also have to be hand-inserted (using the .breakpoint) directive too, all limitations of the text editor.
I've really never known what the EarlyMorning problem really is - as far as I remember, EarlyMorning wouldn't run properly unless it was being run from it's own local directory - Latenite had a hack that modified the working directory first, and EM worked fine (at least, for me).
The workaround isn't needed anymore, and I guess that's what causing the problem
