G-9 2021-06-18 19:33
I’m not familiar with PC, I always coded with my iPhone. I have some issues with my iPhone rn, that’s why I ask you, the best LowRes coders that works on PC, to tell me what program are that using and some good habits.
Thanks, and have a nice holiday :3
P.S. : And nice weekend also 😂
CubicleHead 2021-06-19 02:49
Do you mean as in a text editor?
i use notepad but you can use any text editor
you just save the .nx file then drag it into the lowres nx window
was8bit 2021-06-19 05:25 (Edited)
There is post somewhere on a good PC editor, and someone made a file for it with LOWRES syntax... i cannot remember where that post is....
CubicleHead 2021-06-19 13:25
and this is also helpful:
nathanielbabiak 2021-06-22 00:24 (Edited)
I use Notepad++, it's free! It allows use of a user defined language (UDL), which I've created for LowRes NX's keywords and syntax, and uploaded to my dropbox.
And here's an example of what it looks like in-use: https://www.dropbox.com/s/q9kk32rf8jxwks2/example.PNG?dl=0
(The only limitation is that
EXIT SUB doesn't fold properly, but that is a limitation of the UDL format and not my specific customizations.)
nathanielbabiak 2021-06-22 00:41 (Edited)
As far as good coding habits go, that might be a new subject for the forum! I'm hesitant to offer mine, as (and I'm sure most would agree) LowRes NX is supposed to be fun, so just do whatever works for you. :-)
If you're extremely organized, you can make some monstrous cartridges that do many complicated things. But, there's also plenty of uploads on the site that do one thing really well, like a pretty graphic, a good audio demo, or an interesting algorithm.
"Good coding" can also mean readable code, or something that executes super fast. Unfortunately these objectives are usually mutually exclusive (since we don't have the luxury of optimization-at-compile-time).
Heck, even the manual recommends using
CALL (and avoid using labels,
GOSUB), but it's used by Timo, was8bit, and even me. It's just not a big deal!
Just have fun with it.
was8bit 2021-06-22 02:27 (Edited)
Having fun, i believe, is the unwritten #1 rule ;
Some "tips" are..
use one main DO LOOP with one WAIT VBL like this
- code -
This provides a times loop of exactly 60 frames per second... use code to slow animations or actions if needed, like
W1=(W1+1) MOD 3
IF W1=0 THEN
the code inside this IF THEN has been slowed down to 20 executions/second (60/3)
If you have multiple levels, or other need for it (like a special menu page, etc), it is OK to use more than one DO LOOP ... but for smaller games one DO LOOP will be fine
was8bit 2021-06-22 02:40
Put all of your DIM GLOBAL and other things needed at the top
Put all of your SUBs below your code (and above rom files)
Try to name things to help you remember what you doing in the event you put your code down for awhile, then come back later to it... try to lay out your code so you can read thru it as easily as you read thru a book...
was8bit 2021-06-22 02:53
TIP 3... plan out your graphics to make programming easier... if you want to animate your player running, and you need say 5 images, dont spread the images randomly around... maybe line them up in a row so the code is simpler... i will give you an example with random images, and an example with images in a row....
FOR I=1 TO 5
IF W1=0 THEN
ADD PANI,1,1 TO 5
EXAMPLE:GRAPHICS IN LINE
IF W1=0 THEN
ADD PANI,1,5 TO 10
nwallen 2021-06-25 17:28
For me I used VSCode and setup a script where when F5 is pressed ,in a .nx file, lowres starts with the game loaded. Saves me time when testing.