Post by: johnno56 on July 03, 2018, 04:03:49 am
When a sprite is loaded, it is placed into a 'preview' box. The image is scanned, using the point() command, then places the colour into an array whilst, at the same time, translating the image to the main display. All of this function works just fine... except... the colours are different. See the screen dump. Nothing is done to the pixels. Point picks up the colour and places it in the main display.
Has anyone had this kind of problem before?
J
Post by: johnno56 on July 03, 2018, 07:00:59 am
J
ps: Change the path...
Post by: bplus on July 03, 2018, 07:48:10 am
Code: QB64: [Select]
Post by: johnno56 on July 03, 2018, 08:10:35 am
Many thanks...
J
Post by: Petr on July 03, 2018, 08:37:51 am
Code: QB64: [Select]
Post by: johnno56 on July 03, 2018, 11:26:54 am
J
Post by: johnno56 on July 03, 2018, 09:57:43 pm
This is my first attempt at converting my 'non completed' editor from sdlbasic to qb64. I know, before you say anything, the coding is terribly sloppy.
What works... hmm... interesting...
Colour selection works..
Drawing on the main grid works...
"New" works...
"Load" works but is limited to a specific file...
"Save"... not yet..
"Quit" works... The only part that functioned flawlessly from the start! Who woulda thought?
BIG thanks to bplus and petr for their tips with my colour problem...
Still LOTS to do!! There are FAR too many 'If.. Then's for my liking but it seems to work ok...
As usual, any 'constructive' criticism is welcomed as is any reasonable suggestion (my skills are quite limited... lol)
Let me know what you think?
J
Post by: bplus on July 04, 2018, 08:34:34 am
Post by: johnno56 on July 04, 2018, 09:25:51 am
Yeah, basically (no pun intended)... Trying my hand at converting to QB64. The program is far from finished... crumbs, never got very far with sdl. I know and editor has been 'done to death' and I know that there are other editors 'out there' but I'm not going to learn anything if I don't to it myself.... lol I may never finish it, but that's not the point, is it?
Yeah, I think someone else is trying their hand, using Naalaa. I think I wrote sprEdit in late 2014 and it ended up migrating to Naalaa earlier this year and has been gathering dust ever since... *sigh* Maybe I'll have better luck here... crossed fingers...
Have you tried it yet? I have spent more time on since posting, cosmetics mainly, but slowly plugging away at it... I still need to check out how to save and load to and from the file system... What's the point of writing this beastie if you can't save your work? lol Once that bit is done then I can start looking at how to implement other drawing tools. eg: circles (ellipses); boxes; lines; fill (the dreaded fill - my aching back...) Perhaps different modes? ie: 8x8, 16x16 etc. (my very early version had these... but I think I lost it in a drive crash... Just simple 'buttons' containing "8" and "16" and the main grid would change accordingly (handy for retro sprites)... anyway, just some ideas... Saving to files.... hmmm...
Post by: bplus on July 04, 2018, 09:40:01 am
I'd say work on saving a file to same folder as source, use a time stamped name so you don't have to worry about getting input about file name from user or loosing your title 01 sample file. Let Windows or your OS do the work of renaming the file if you really want to save the file with a real name.
Too much concern for color names for my taste, but not my app! ;-))
Naalaa was nice little editor, we had gone a long way with it. I will see if I can dig it up. ;)
Post by: johnno56 on July 04, 2018, 10:12:46 am
My very first version was tedious. I had a colour patch with way more colours than a bag of Skittles and each colour square had it's rgb code and paint command... sore fingers THAT day!! You're right about the names. They are only there for my benefit. It's simple enough just to leave out.
I'm still toying with the idea to change the colour patch... the current one seem to be all over the place.
Hey. I went looking for the first version on another disc and found it... Horrible code. Simply horrible. I don't know what I was thinking. But it DID have two main grid sizes 10 an 20 pixels (for 16x16 and 32x32)
Well. It's just gone midnight and my eyes are struggling to stay open... I've started tidying up the listing a little by using subs and comments. Since the last version I had put all the colour names and rgb codes into an external file. Made for a slightly smaller listing... I'll do some more in the morning, and if I remember, I may post an update. But, it's only cosmetic, no real advancement... lol
My mug of coffee has finally worn off... Goodnight.
J
Post by: bplus on July 04, 2018, 10:23:44 am
Post by: Petr on July 04, 2018, 11:00:26 am
Galleon´s save utility:
Code: QB64: [Select]
- 'program create file CIRCLE.BMP on your harddrive (tested in windows)
- _DEST circleimage&
- SaveImage circleimage&, "CIRCLE.BMP"
- _FREEIMAGE circleimage&
- lastsource& = _SOURCE
- _SOURCE image&
- r$ = ""
- NEXT px&
- d$ = d$ + r$ + padder$
- NEXT py&
- _SOURCE lastsource&
- b$ = b$ + d$ ' total file data bytes to create file
- f& = FREEFILE
- CLOSE #f&
Post by: FellippeHeitor on July 04, 2018, 12:08:05 pm
Post by: FellippeHeitor on July 04, 2018, 12:22:31 pm
Post by: bplus on July 04, 2018, 12:34:00 pm
Johnno needs to update image as drawn, already tested Petr's save, worked great!
Post by: bplus on July 04, 2018, 12:36:36 pm
Post by: johnno56 on July 04, 2018, 04:21:52 pm
The dll reffered to is 'zlib1'
I'm going to go out on a limb here and suggest that the saveimage library is for Windows only.... Just a guess.
J
Post by: FellippeHeitor on July 04, 2018, 04:32:02 pm
If anyone using Windows would like to try the library, just make sure to fix SaveImage.BI file to make the declare library line reference the .dll file using a relative path by adding ".\" to the file name:
Code: QB64: [Select]
Post by: johnno56 on July 04, 2018, 05:00:24 pm
Using variations of "get" and "put" still requires the user to "remember" the name of the file to load (or do a previous search for the filename)
This is exactly the same problem I had when I first started this editor using sdlbasic back in 2014. The upside is that I have learned some stuff about QB64 that I didn't know before... Cool.
Now. How about a nice game of Pong.... lol
Post by: FellippeHeitor on July 04, 2018, 05:21:20 pm
Post by: Petr on July 04, 2018, 05:45:05 pm
Unfortunately, I can not help you with program for selecting files on a Linux disk if you mean this and you want to move around on the disk to select the file for editing. I have none knowledge in this - in Linux.
Code: QB64: [Select]
- 'sprite editor - base:
- 'first i load a picture and show it in grid:
- IF _MOUSEWHEEL THEN grid = grid + _MOUSEWHEEL: LINE (10, 10)-(500 + grid, 500 + grid), _RGB32(0, 0, 0), BF
- CreateGrid D(), 10, 10, 500, 500, grid, a, b
- 'keyboard for grid move (arrows)
- cellsX = (500 - 10) / grid
- cellsY = (500 - 10) / grid 'so is writed call for CreateGrid, for X is 1st and 3th parameter, for Y is 2nd and 4th parameter
- xx = a: yy = b 'draw start array values
- clr& = D(xx, yy)
- xx = xx + 1
- NEXT X
- yy = yy + 1
- xx = a
- NEXT Y
- x = x + 1
- NEXT h&
- y = y + 1: x = 0
- NEXT y&
- _MEMFREE m
Post by: johnno56 on July 04, 2018, 05:52:56 pm
I'm running with Linux... Even though I am using the Linux version of QB64, it usually always boils down to, 'It's a Linux/Windows thing'... Maybe, if I leave the editor 'on the shelf' for another 4 years, I may try again... lol
I need coffee...
Petr,
Thank you for the code sample and your advice... I am not using Windows...
This is the part were I duplicate the message to Fellippe... lol
I still need coffee...
J
Post by: bplus on July 04, 2018, 06:01:58 pm
As for getting files from current folder from which to select and load, also should be able to do in Linux.
But it would be easier if can clear screen to display list of files from which to pick and then be able to redisplay editor.
Post by: Petr on July 04, 2018, 06:04:09 pm
Post by: Petr on July 04, 2018, 06:14:18 pm
Quote
As for getting files from current folder from which to select and load, also should be able to do in Linux.
But it would be easier if can clear screen to display list of files from which to pick and then be able to redisplay editor.
This is exactly what I'm going to write if we find out how to list the contents of a linux disk into a text file. I've already done it under windows, so when we get a text file under linux, that's just the different SHELL command.
Post by: Petr on July 04, 2018, 06:21:10 pm
Post by: johnno56 on July 04, 2018, 11:17:14 pm
ls *.bas > files.txt works just fine and the list is sorted...
J
Post by: SMcNeill on July 05, 2018, 01:04:53 am
It does use the dll that Steve provides in the package so yes, it's Windows only (and I failed to remember you're a Linux user, sorry about that).
If anyone using Windows would like to try the library, just make sure to fix SaveImage.BI file to make the declare library line reference the .dll file using a relative path by adding ".\" to the file name:Code: QB64: [Select]
I'm thinking the library should still work for Linux users, as long as you point it to where zlib puts itself on your machine.
go to
System->Administration->Synaptic Package Manager
search for zlib1g-dev and install the package.
Of course, it's not going to find a *.dll file, but there should be a Linux equivelant to work off of. QB64 SDL used to require ZLIB, and it worked on Linux, so somebody out there should be able to patch it all together to work. (At least, I'd hope so.).
Post by: johnno56 on July 05, 2018, 03:12:53 am
J
Post by: Petr on July 05, 2018, 04:03:58 am
Quote
ls *.bas > files.txt works just fine and the list is sorted...
Johnno56, please add this file as an attachment, and I will work on it. If you just want to browse the current folder, do this list without subdirectory names, but if you want to browse disk, then do it with subdirectory names. I want it to see how Linux marks folders (windows writes <DIR>) and whether the file contains characters for text formatting or not and also whether it contains a header or not. Because your editor will probably support more than just one format, you can not use the mask as * .BMP> file.txt, but better *. * , the appropriate files will then be filtered in program from this listing. So my program return then output for all PNG, BMP, JPG, GIF from this one text file.
Post by: johnno56 on July 05, 2018, 05:12:34 am
If you want to see directories, the "ls" command will need to be told to include them. I am not familiar with all of the parameters for the "ls" command. This one I have used to create the file 'ls -l -a *.* > myfiles.txt
In the file, the character "d" at the begining of each record, indicates a directory.
I hope this helps.
J
Post by: Petr on July 05, 2018, 05:20:16 am
Post by: Petr on July 05, 2018, 06:06:58 am
Code: QB64: [Select]
- 'user = 1
- SHELL cmd$ 'commented, because you use Linux
- F = FREEFILE
- infilePos = infilePos + 1
- D = D + 1
- Fi = Fi + 1
- F = FREEFILE
- infilePos = infilePos + 1
- D = D + 1
- Fi = Fi + 1
- Filter Filess(), "BMP JPG GIF PNG"
- NEXT Dl
- NEXT Dl
- oldmask$ = newmask$
- listmask(li) = newmask$
- li = li + 1
- NEXT S
- 'sort files in array by mask:
- newfil(nn) = fil(Sort): nn = nn + 1
- 'replace incomming array with filtered content:
- fil(rewr) = newfil(rewr)
- NEXT rewr
- ERASE newfil
- ERASE listmask
Post by: johnno56 on July 05, 2018, 06:59:21 am
Subscipt out of range
The filelist.txt file is created. Screen clears and only "Directories List:" is displayed then the error appears.
Post by: Petr on July 05, 2018, 07:31:51 am
Code: QB64: [Select]
- 'user = 1
- SHELL cmd$
- F = FREEFILE
- infilePos = infilePos + 1
- D = D + 1
- Fi = Fi + 1
- F = FREEFILE
- infilePos = infilePos + 1
- D = D + 1
- Fi = Fi + 1
- Filter Filess(), "BMP JPG GIF PNG"
- NEXT Dl
- NEXT Dl
- oldmask$ = newmask$
- listmask(li) = newmask$
- li = li + 1
- NEXT S
- 'sort files in array by mask:
- newfil(nn) = fil(Sort): nn = nn + 1
- 'replace incomming array with filtered content:
- fil(rewr) = newfil(rewr)
- NEXT rewr
- ERASE newfil
- ERASE listmask
Post by: johnno56 on July 05, 2018, 08:07:04 am
Directories list:
Found Directories:-1
Moments later an error:
Unhandled error #9
Line: 66 (in main module)
Subscipt out of range
Continue?
Yes No
Post by: Petr on July 05, 2018, 08:29:11 am
Good. File size fileslist.txt is not 0 bytes? Please try this again.
Code: QB64: [Select]
- 'user = 1
- SHELL cmd$
- _DELAY 1
- F = FREEFILE
- infilePos = infilePos + 1
- D = D + 1
- Fi = Fi + 1
- n:
- F = FREEFILE
- infilePos = infilePos + 1
- D = D + 1
- Fi = Fi + 1
- Filter Filess(), "BMP JPG GIF PNG", numfiles
- NEXT Dl
- NEXT Dl
- SLEEP 2
- 'text file test:
- PRINT "test created file:"
- CLOSE #F
- PRINT ff$
- oldmask$ = newmask$
- listmask(li) = newmask$
- li = li + 1
- NEXT S
- 'sort files in array by mask:
- newfil(nn) = fil(Sort): nn = nn + 1
- 'replace incomming array with filtered content:
- fil(rewr) = newfil(rewr)
- NEXT rewr
- ERASE newfil
- ERASE listmask
Post by: Petr on July 05, 2018, 08:45:16 am
Code: QB64: [Select]
maybe this is the problem, bacause i write it without space between > and filelist.txt
Post by: johnno56 on July 05, 2018, 09:22:38 am
It said that it found directories but did not display them.
Found 8 files and displayed various graphics files of different formats.
Then displayed the filelist.
Maybe the list I provided is not what is needed. I will attach the "ls" command manual for you to read... It's not really a manual... That is what Linux calls it. It's about 2 or 3 pages long. Perhaps you can make some sense of it all... I'm getting too tired to think straight...
J
Post by: bplus on July 05, 2018, 09:30:43 am
I know the Load button could made into a drop down list box when you guys manage to get files data from OS.
Post by: bplus on July 05, 2018, 09:49:43 am
Open a file explorer in your favorite OS
Then copy/paste a file name from clipboard Or just type the dang thing out. I hear Linux users love to type. ;-))
Post by: bplus on July 05, 2018, 10:05:26 am
More thoughts on using InForm:
Instead of loading a limited color palette, you could use 3 slider bars for RGB and create custom colors on the fly!
Think of all the code that could be slashed from the Sprite Editor with just that one move!
Post by: bplus on July 05, 2018, 10:11:46 am
Hmm... I wonder about reversing that process, click a point from the blown up image and set color selector to that color (along with the slider bars).
Post by: FellippeHeitor on July 05, 2018, 10:23:46 am
Post by: bplus on July 05, 2018, 12:11:46 pm
Do you know of any InForm apps that did use 3 sliders for RGB, seems to me it would be THE Demo for slider bars.
Post by: FellippeHeitor on July 05, 2018, 01:17:54 pm
Post by: bplus on July 05, 2018, 01:29:44 pm
Thanks Fellippe
Post by: Petr on July 05, 2018, 03:13:03 pm
Post by: Petr on July 05, 2018, 03:45:27 pm
Quote
Modify
Hmm... I wonder about reversing that process, click a point from the blown up image and set color selector to that color (along with the slider bars).
It is not difficult. This is a normal percent example: You have a R bar, a G bar and a B bar. 0% is on the left and it is 0. 100% is on right, the value for R and G i B is maximum 255. So if it loads with the POINT or _MEMGET command a pixel of the image, the function returns three R, G, B values. For example the color _RGB32 (128,255,0), so 128 is exactly 50 percent of 256, the driver for R is set in the middle. 255 for G is 100 percent, that set driver to the right. B is 0, ie zero percent. The driver for B will be at the beginning. On the same principle working drivers in my SNDRAW player.
Post by: johnno56 on July 05, 2018, 05:39:52 pm
In regards to installing Linux, now days, it's not hard at all. You mentioned an "older" notebook... Some of the mainstream versions of Linux, as with newer versions of Windows, will probably be a bit sluggish on older machines mainly because the newer OS's can be quite taxing on older systems.
Linux has installations for older machines... Yay! Ubuntu has Lubuntu and Xubuntu for example... All you do is go to their homepage; Download the ISO image; Burn it to a DVD or USB drive; Pop it into the notebook and boot. You can either install or test it without installing... Just in case... lol
[abandoned, outdated and now likely malicious qb64 dot net website - don’t go there] has both 32 and 64 bit versions for Linux. (Oh no! [abandoned, outdated and now likely malicious qb64 dot net website - don’t go there] has problems! No. the main website is fine. It seems that the Forums are "on the fritz"...)
If you need help... You know where I am... lol
J
Post by: Petr on July 06, 2018, 03:45:19 pm
Code: QB64: [Select]
- _PUTIMAGE , i&
- R = Drive(600, 20, 255, Red)
- g = Drive(600, 40, 255, green)
- b = Drive(600, 60, 255, blue)
- Drive = (vlue / max) * 100
- l2 = xpos + Drive
Post by: Petr on July 06, 2018, 03:54:29 pm
Post by: johnno56 on July 06, 2018, 07:41:21 pm
I have decided to shelve the Sprite Editor. I originally started it to, "See if I could", but came up against what "I" call a problem, of simply loading and saving each project. I ended up with the same problem using sdlbasic (original version) as I am now having with QB64. Projects can eventually be saved and loaded but not 'simply'. I feel the amount of work needed to complete the project kind of out weighs the concept of a "simple" editor. You guys have put in more work than I could have hoped for and for that I'm very appreciative. I think from now on I will restrict my ideas to what I can actually achieve...
Thanks guys.
J
Post by: FellippeHeitor on July 06, 2018, 10:03:03 pm
Post by: SMcNeill on July 07, 2018, 02:02:13 am
Steve also has a file select library that's cross platform, maybe he could repost it.
http://qb64.freeforums.net/thread/63/file-directory-listing-arrays
Try the above. It's not a GUI file selection tool, but it's a crossplatform way to get information into a set of directory and file arrays. I've got a GUI version around here somewhere as well, but most folks just seem to enjoy making their own interface and using the stripped down version here to get the information they need, instead. ;)
Post by: Petr on July 07, 2018, 04:29:06 am
Post by: bplus on July 08, 2018, 12:29:29 pm
Post by: bplus on September 07, 2020, 04:42:54 pm
Code: QB64: [Select]
- ' =========================================================
- '
- ' SPRITE DRAW v03 by johnno b+ mods 2020-09-07 comment with " '<
- '
- ' =========================================================
- _DELAY .25
- 'DIM SHARED clr AS _UNSIGNED LONG
- gridsize = 64
- gsize = 9
- psize = 1
- tools = 5
- resetcurrentcolour = 0
- symmetry = 0
- exist = 0
- ' < for ? don't need
- 'r5 = 0
- 'g5 = 0
- 'b5 = 0
- zones = 9 ' < mouse cleck areas
- quit = 0
- 'mousegridx = 0
- 'mousegridy = 0
- 'mousegridx2 = 0
- 'mousegridy2 = 0
- 'DIM SHARED bgrid(gridsize, gridsize)
- 'DIM SHARED prevgrid(gridsize, gridsize)
- 'PRINT sample '< got it
- 'end ' < test sample load
- setup '< dang where is sample
- ' Wait for mouse movement or button press
- '
- mx = _MOUSEX
- my = _MOUSEY
- ' ----------------------------
- ' Determine Mouse Zone
- ' ----------------------------
- ' Zone 1 - Main Grid
- '
- zone(1) = 1
- zone(1) = 0
- ' Zone 2 - NEW Button
- '
- zone(2) = 1
- zone(2) = 0
- ' Zone 3 - LOAD Button
- '
- zone(3) = 1
- zone(3) = 0
- ' Zone 4 - SAVE Button
- '
- zone(4) = 1
- zone(4) = 0
- ' Zone 5 - QUIT Button
- '
- zone(5) = 1
- zone(5) = 0
- ' Zone 6 - PENCIL Button
- '
- zone(6) = 1
- zone(6) = 0
- ' Zone 7 - LINE Button
- '
- zone(7) = 1
- zone(7) = 0
- ' Zone 8 - MIRROR Button
- '
- zone(8) = 1
- zone(8) = 0
- ' Zone 9 - CLEAR Button
- '
- zone(9) = 1
- zone(9) = 0
- ' --------------------
- ' Draw On Grid
- ' --------------------
- drawongrid
- ' -----------------------
- ' Erase From Grid
- ' -----------------------
- erasefromgrid
- 'updatepreview ' < should these be outside IF?
- 'redrawgrid
- ' ------------
- ' QUIT
- ' ------------
- _DELAY .2
- COLOR darkred
- COLOR red
- _DELAY .2
- quit = 1
- ' ------------------
- ' LOAD Image
- ' ------------------
- _DELAY .2
- tool(1) = 0
- pencil
- loadfile
- ' ------------------
- ' SAVE Image
- ' ------------------
- _DELAY .2
- 'savefile
- ' -----------------
- ' NEW Image
- ' -----------------
- _DELAY .2
- newimage
- ' -------------------
- ' CLEAR Image
- ' -------------------
- _DELAY .2
- clearimage
- ' ----------------------
- ' TOOLS - Pencil
- ' ----------------------
- _DELAY .2
- tool(1) = 1
- pencil
- tool(2) = 0
- drawline
- tool(3) = 0
- symmetry = 0
- mirror
- ' --------------------------
- ' TOOLS - Line (wip)
- ' --------------------------
- _DELAY .2
- 'tool(1) = 1
- 'pencil
- 'tool(2) = 1
- 'drawline
- 'tool(3) = 0
- 'symmetry = 0
- 'mirror
- ' ---------------------------------
- ' TOOLS - Mirror / Symmetry
- ' ---------------------------------
- _DELAY .2
- tool(1) = 1
- pencil
- tool(2) = 0
- drawline
- tool(3) = 1
- symmetry = 1
- mirror
- ' -----------------------------
- ' Select Current Colour
- ' -----------------------------
- 'convert (currentcolour)
- 'r5 = getR(currentcolour)
- 'g5 = getG(currentcolour)
- 'b5 = getB(currentcolour)
- COLOR currentcolour
- _DELAY 2
- '==================================================================
- ' ----------------------
- ' Convert to RGB
- ' ----------------------
- 'SUB convert (clr)
- ' r5 = _RED32(clr)
- ' g5 = _GREEN32(clr)
- ' b5 = _BLUE32(clr)
- 'END SUB
- ' ==================================================================
- '
- ' PROCEDURES AND FUNCTIONS
- '
- ' ==================================================================
- ' -----------------------
- ' Initial Display
- ' -----------------------
- SUB setup
- gsize = 9
- ' ------------------------
- ' Reset Tool flags
- ' ------------------------
- tool(i) = 0
- ' ------------------------
- ' Reset Zone flags
- ' ------------------------
- zone(i) = 0
- ' ----------------------
- ' Draw Main Grid
- ' ----------------------
- COLOR gridcolour
- x = x + gsize
- y = y + gsize
- 'redrawgrid
- ' ---------------------
- ' Program Logo
- ' ---------------------
- ' -----------------------------
- ' Colour Selection Grid
- ' -----------------------------
- ' ----------------------------------
- ' Sprite Preview Box - 64x64
- ' ----------------------------------
- COLOR gridcolour
- COLOR gray
- 'update grid
- preview2grid
- ' -----------------------------------------
- ' Sprite Preview Box - Magnified x2
- ' -----------------------------------------
- COLOR gridcolour
- COLOR gray
- ' -----------------------------------
- ' Current Selected Colour Box
- ' -----------------------------------
- COLOR gridcolour
- ' --------------------
- ' Menu Buttons
- ' --------------------
- COLOR gridcolour
- COLOR gridcolour
- COLOR gridcolour
- COLOR gridcolour
- COLOR gridcolour
- ' --------------------
- ' TOOL BUTTONS
- ' --------------------
- ' Pencil
- COLOR gridcolour
- tool(1) = 0
- ' Line
- COLOR gridcolour
- COLOR gridcolour
- tool(2) = 0
- ' Mirror / Symmetry
- COLOR gridcolour
- tool(3) = 0
- ' Spares
- SUB drawongrid
- COLOR currentcolour
- COLOR currentcolour
- SUB erasefromgrid
- SUB newimage
- sure
- savefile
- exist = 0
- tool(1) = 0
- pencil
- tool(2) = 0
- drawline
- tool(3) = 0
- symmetry = 0
- mirror
- maingrid(imagex, imagey) = black
- ' -------------------------
- ' "Poor Man's" Fill
- ' -------------------------
- 'r5 = getR(maingrid[imagex][imagey])
- 'g5 = getG(maingrid[imagex][imagey])
- 'b5 = getB(maingrid[imagex][imagey])
- 'set color r5,g5,b5
- dotx = imagex * 10
- doty = imagey * 10
- ' --------------------
- ' Draw Preview
- ' --------------------
- ' ------------------------------
- ' Draw Magnified Preview
- ' ------------------------------
- resetcurrentcolour = 1
- redrawgrid
- _DELAY .1
- 'free file 1
- SUB loadfile
- COLOR gridcolour
- ' --------------------
- ' SCAN IMAGE ?
- ' --------------------
- ' -------------------------------
- ' TRANSFER TO MAIN GRID ?
- ' -------------------------------
- ' -------------------------
- ' "Poor Man's" Fill
- ' -------------------------
- 'r5 = getR(maingrid[imagex][imagey])
- 'g5 = getG(maingrid[imagex][imagey])
- 'b5 = getB(maingrid[imagex][imagey])
- 'set color r5,g5,b5
- dotx = imagex * 10
- doty = imagey * 10
- redrawgrid
- SUB savefile
- SUB clearimage
- tool(1) = 0
- pencil
- tool(2) = 0
- drawline
- tool(3) = 0
- mirror
- maingrid(imagex, imagey) = black
- ' -------------------------
- ' "Poor Man's" Fill
- ' -------------------------
- 'r5 = getR(maingrid[imagex][imagey])
- 'g5 = getG(maingrid[imagex][imagey])
- 'b5 = getB(maingrid[imagex][imagey])
- 'set color r5,g5,b5
- dotx = imagex * 10
- doty = imagey * 10
- ' --------------------
- ' Draw Preview
- ' --------------------
- ' ------------------------------
- ' Draw Magnified Preview
- ' ------------------------------
- resetcurrentcolour = 1
- redrawgrid
- _DELAY .1
- 'free file 1
- SUB sure
- exist = 0
- exist = 1
- SUB msgbox
- ' -----------------------
- ' TOOL PROCEDURES
- ' -----------------------
- SUB pencil
- COLOR gridcolour
- COLOR white
- COLOR yellow
- COLOR gridcolour
- tool(2) = 0
- drawline
- tool(3) = 0
- symmetry = 0
- mirror
- SUB drawline
- ' -------------------------------------
- ' Change state of 'line' button
- ' -------------------------------------
- 'IF tool(2) = 0 THEN
- 'COLOR gridcolour
- 'LINE (1014, 148)-STEP(80, 40), , B
- '_PRINTSTRING (1022, 151), "Line"
- 'END IF
- 'IF tool(2) = 1 THEN
- 'COLOR white
- 'LINE (1014, 148)-STEP(80, 40), , B
- 'COLOR yellow
- '_PRINTSTRING (1022, 151), "Line"
- 'COLOR gridcolour
- 'END IF
- ' -----------------------------------------
- ' Line function goes here... W.I.P.
- ' -----------------------------------------
- 'COLOR currentcolour
- 'x1 = 0
- 'x2 = 0
- 'y1 = 0
- 'y2 = 0
- 'click = 0
- 'WHILE click = 0
- 'IF _MOUSEBUTTON(1) AND zone(1) = 1 THEN
- 'click = 1
- 'x = _MOUSEX
- 'y = _MOUSEY
- 'x1 = x
- 'y1 = y
- 'mousegridx = INT(x1 / 10) * 10
- 'mousegridy = INT(y1 / 10) * 10
- 'LINE (mousegridx, mousegridy)-STEP(10, 10), , BF
- 'END IF
- 'IF mb2 AND zone(1) = 1 THEN
- ' x = _MOUSEX
- 'y = _MOUSEY
- 'x2 = x
- 'y2 = y
- 'mousegridx = INT(x2 / 10) * 10
- 'mousegridy = INT(y2 / 10) * 10
- 'LINE (mousegridx, mousegridy)-STEP(10, 10), , BF
- 'click = 1
- 'dx = ABS(x2 - x1)
- 'sx = -1
- 'IF x1 < x2 THEN sx = 1
- 'dy = ABS(y2 - y1)
- 'sy = -1
- 'IF y1 < y2 THEN sy = 1
- 'er = -dy
- 'IF dx > dy THEN er = dx
- 'er = INT(er / 2)
- 'DO
- ' LINE (INT(x1 / 10) * 10, INT(y1 / 10) * 10)-STEP(10, 10), , BF
- 'e2 = er
- 'IF e2 > -dx THEN
- ' er = er - dy
- 'x1 = x1 + sx
- 'END IF
- 'IF e2 < dy THEN
- ' er = er + dx
- 'y1 = y1 + sy
- 'END IF
- '_DISPLAY
- 'LOOP UNTIL x1 = x2 AND y1 = y2
- 'END IF
- '_DISPLAY
- 'IF INKEY$ = CHR$(27) THEN SYSTEM
- 'WEND
- 'END IF
- SUB mirror
- '
- ' Change state of 'symmetry' button
- '
- COLOR gridcolour
- COLOR white
- COLOR yellow
- COLOR gridcolour
- SUB redrawgrid
- gsize = 9
- COLOR gridcolour
- x = x + gsize
- y = y + gsize
- SUB updatepreview
- ' Magnified Preview
- 'REM draw rect 800+(prevx*2),100+(prevy*2),2,2,true
- SUB preview2grid '< this whole sub
Hey looks like we are ready to save an image ;-)
And looks like we will need a tool to set current color from the image!
Post by: johnno56 on September 07, 2020, 05:32:35 pm
Post by: johnno56 on September 07, 2020, 06:19:31 pm
I have cobbled together an 'eyedrop' function that will select a colour from the main grid... There maybe bugs... (no surprises there... lol) Give it a test and if it's ok then we'll keep it....
The attached file is only the main program.
Post by: bplus on September 07, 2020, 07:57:36 pm
Post by: bplus on September 07, 2020, 08:54:44 pm
SaveImage will not save if it finds a file with save name already existing, it also has a number of other numbered error messages. I just moved on whether the file actually got saved or not. But you can find out if file actually did get saved or what kind of error. It's in the giant BM file.
I also decreased screen width a shade and centered to my screen to just fit out from under my tool bar.
I also put a _LIMIT in the main loop to save me from CPU fan noise!
So here is v03b with save image:
Post by: johnno56 on September 08, 2020, 12:47:57 am
Post by: johnno56 on September 08, 2020, 01:10:16 am
Saving and loading worked as you had coded. Cool.
I had made some changes to version 3 while you were working on 3b... The mods were mainly around the messagebox routine and a few messages. No drama. I will add the changes to 3b... Somebody has to move to someone's timezone... lol Hmm... That could be difficult. I cannot go more that 5kms from home (a few exceptions) and the Victorian borders have been closed. So you cannot move here.
Can you imagine if we both made significant changes? Oh the duplication of effort... There has to be a better way to manage projects remotely.... Any ideas?
Post by: johnno56 on September 08, 2020, 02:21:38 am
I think the message box system, although works, could do with an overhaul... lol
"Line" has been hard coded with a message.
"Save" message works.
Note: I think a scan of the main grid prior to saving may be in order. Even though the main grid is "blank" the save function will store an empty sprite...
Not sure if the "lucon" font is needed...
I have removed the far right button... just in case...
Anyway. Give it a test and see what you think?
Post by: bplus on September 08, 2020, 10:52:56 am
The size of the screen is fine. If you need it to be smaller (in width) then the "spare box" to the far right can be removed. It was only put there to gauge the width of three sets of buttons.
Good but I am optimistically hoping we will eventually need that many buttons! But if they stay the same size, they could be shifted a tiny bit to get and keep overall screen width to where I had it set. 1300 is just over my screen limit with my toolbar along the left side of screen.
Quote
Saving and loading worked as you had coded. Cool.
This is very good news that I'm so glad to have confirmed. Yeah Steve McNeill!
Quote
I had made some changes to version 3 while you were working on 3b... The mods were mainly around the messagebox routine and a few messages. No drama. I will add the changes to 3b... Somebody has to move to someone's timezone... lol Hmm... That could be difficult. I cannot go more that 5kms from home (a few exceptions) and the Victorian borders have been closed. So you cannot move here.
Perhaps this would be a good time, to mention I have a pop up Dialog type Message Box you can move around the screen and then closes and gone with message read. I also have a pop up Input Box you also can move around the screen. Altogether they would be maybe another 300 lines of code?
Quote
Can you imagine if we both made significant changes? Oh the duplication of effort... There has to be a better way to manage projects remotely.... Any ideas?
Yeah I had already duplicated an effort of yours by loading the sample at startup and making a preview2grid subroutine. You already had all that in the Load button!
But we have done alright in the past working together on projects: Battleship, Blackjack... and that's just the B's ;-))
Well you are in charge of the Official Code versions in this project I will just offer mods to be assimilated into it or not adding a b at end of version number to distinguish code sets.
Post by: bplus on September 08, 2020, 11:05:43 am
Ok. I have merged v3 and v3b into v4.
I think the message box system, although works, could do with an overhaul... lol
"Line" has been hard coded with a message.
"Save" message works.
Note: I think a scan of the main grid prior to saving may be in order. Even though the main grid is "blank" the save function will store an empty sprite...
Not sure if the "lucon" font is needed...
I have removed the far right button... just in case...
Anyway. Give it a test and see what you think?
Yeah, how married to your message box system are you? I am sorry I had forgotten I had worked out a Message Box dialog that you can move around the screen and then close. Same with an Input Box. So you might want to see those before going further with built in one on your main screen.
And the Tiny Navigator app might be just the thing for retrieving filenames but it also has a rather large set of lines of code and would be done on a whole separate screen.
It's like I've been building tools (except for save image) with this program in mind. eg I have a color picker too that employs slide bars but I think I like the point and click style better that Dav is working on for this kind of app and that Ken used with one of his Paint Programs.
Well while you sleep, the night shift elves will be working on adding tools to version #4. ;-))
Post by: johnno56 on September 08, 2020, 12:31:30 pm
It's about 2:30am and I'd better get some sleep. Sat through the original 1960 'Time Machine' AND the 2002 version back to back... Can't get enough of H.G....
BIG day tomorrow... hopefully... Our coffee delivery should arrive.... Moo Ha Ha...
Post by: bplus on September 08, 2020, 05:27:32 pm
Just started going over version 4 and 2 notes:
1) Include all files needed to run the bas code in the package so people wont have to be looking all over for stuff.
also if you want to use a special font include it in the zip package.
PPS if you are worried about cluttering up forum with attachments, we can delete old abandoned ones as the new ones come to replace them as with Blackjack.
2) Don't forget to update the title / header label of program, v04 here. With all sorts of copies about this is needed to sort out which it is we are looking at. I am trying to keep an untouched copy of your newest program and one that I am modifying plus backup files of older versions.
PS your message box looks good and works :)
Post by: johnno56 on September 08, 2020, 07:09:03 pm
Clutter on a forum? Interesting turn of phrase... Isn't what we are all submitting a 'type' of 'clutter'? lol
No. I'm not concerned about forum clutter. That responsibility usually falls to either the site Admin or the forum host. But we should be mindful of how much we contribute... To that end... We have all been given the ability to create and edit our own posts so perhaps we could be given the ability to only delete our own posts... Just thinking outside the box... We should make it a habit, ok "I" should make it a habit, to properly manage my backups and leave 'site clutter' management to those who do it so well...
Title headers.... I almost always forget about those... Good point.
Message box. It's a drastically modified "Perter" version. It's not Peter's but it will do until something better comes along. Thanks anyway. That might be an interesting project... A message box library... This is the part where someone says, "But we already have a library for that." and totally destroy one of my few ideas... Story of my life.... *sigh*
Coffee time!
Post by: bplus on September 09, 2020, 12:18:04 am
I have to warn when you Load a file you have to press f to get the real filenames list up. The one showing on the right is just a 20 file sample of the whole list that is loaded into an array that you can scroll, mouse click, arrow key, page home end... even type in item number and enter, all these options to select a file off the listing. And if you change your mind use top right X or escape.
Oh yeah, I included a copy of direntry.h and Readme.txt file that reminds you to make sure you have a copy of this in your QB64 folder. This is so, hopefully, the file name retriever can work both in Windows and Linux.
Some screen shots from SprDraw04b and the zip is last attachment:
Post by: johnno56 on September 09, 2020, 12:29:57 am
Post by: bplus on September 09, 2020, 12:33:46 am
Oh you are going to keep me hanging in suspense :)
Post by: johnno56 on September 09, 2020, 01:21:09 am
Post by: bplus on September 09, 2020, 01:31:10 am
Yes. I can load files.... Cool...
Yeah! Yea to Steve there is allot of his influence in that code!
I know its annoying to have to press f to get the files list up. It was a way for mouse and keypresses to work on just one list at a time. I will work on that. I'll also have a look at the drawing circles and lines that you have penciled in.
Might try a fill like Paint? Have you any requests?
Post by: johnno56 on September 09, 2020, 02:02:28 am
For sprites 16x16 and up... Maybe a texture fill. There was a really old Amstrad (8 bit) that used a user-made texture fill. Amstrad CPC464 did not have a paint or fill command. The standard 4-way fill routine would work but was painfully slow... I have pretty much all of Amstrads programs, games and magazines... I will begin a search... manually... yikes!
Post by: bplus on September 10, 2020, 12:07:34 pm
Quick question, were the buttons setup to use the Lucon font? I ask because they are all aligned to top left corner and that would be what would happen if a bigger font were expected to be used. Are you using a Windows version of Lucon? I would like a copy if not. I am overhauling the code so I can add the drawing tools line, circle, fill, undo...
Also need more idea about what "textures" are, like checkerboards of colors or gradients of colors or...?
So far 469 LOC eliminated plus some more safety checks with LoadFile still far from idiot proof but at least you wont accidentally KILL QB64.exe ;-)) or any other files except png, jpg, bmp plus some save to file checks at newImage, Quit, LoadFile.
Post by: bplus on September 10, 2020, 05:25:19 pm
hmm... now I see a little misalignment, back to drawing board ;-) Lines sure look ragged!
Post by: johnno56 on September 11, 2020, 08:30:40 am
In reference to the 'jagged' line... Just the other day, while researching line drawing, I read something about how to 'neaten' the line.... I only wish I could remember where I read it. It was just a passing note and didn't give it much thought... Don't you just hate that?
I am going to assume that the "Get Hue" button implies that the "default" drawing colour is now White? Cool.
In regards to textures. Mainly "fill patterns". Cherry Paint was written to be used on the Amstrad... Ugly as... But that was the mid 80's... lol
See attached...
Post by: bplus on September 11, 2020, 10:22:13 am
Here is something to make note of: the default font in QB64 is 8 pixels wide and 16 pixels high (you can specify _FONT 8 for drawing special ASCII Characters, those are 8x8 and switch back and forth with _FONT 16, did you see my ASCII dice game?). You need to know that often in QB64 unless in screen mode 0 or as you say using your own font. I've been partial to Arial for clean lines ttf. If you don't, you should keep notes to track QB64 and the other Basics you use, QB64 is the one with all the Type stuff :)
QB64 should do Font width and height like they do Image width and height because after all it is an image too.
And images could be concatenated like printing font so you can tile a whole background with a strings of tile numbers.
Anyway, Get Hue is my name for what you called "Eye dropper". I didn't think "eye dropper" is too common but maybe "Get Hue" is obscure too, just remember Hue is the guy with all the colors in the grid ;-)) I didn't think it was really a drawing tool but you have to deactivate all the others so your mouse click on the grid picks up the color. So I put it 1st under drawing tools. For Mirror, not a drawing tool but an drawing tool enhancement is just a flag you toggle on and off.
I got rid of zones and tools and track drawing mode with a letter and zone click is handled right there in main loop with left mouse button on, jobbed out to a sub if code is longer than a dozen lines. BTW what is difference between your right click "erase" and just setting color to background? None, I think, so no right mouse click stuff at moment but might be changed for popup menu for file stuff of maybe cherry picking color patterns like in your snapshot. That snapshot is loaded with ideas!
Yeah, icons for drawing tools much better than words! I am thinking your message box might be helpful for tool tips and helping instruct for more complicated too operations.
RE: Real Sprites!
So far what we are making are really tiles and restricted to square ones @64x64 eh...
I have been wondering how to do transparent color for real sprites, no background, just the object image like I did with Templar Cross. PNG files dont work well there is always background black when you take a point reading to save an image.
I am thinking a new extension .trn for transparent or .clr for clear so we can just layer an object image over everything behind it. Will need our own loadimage say loadSprite, easy enough I think.
What do you all think? Am I reinventing a wheel here?
Hmm... on second thought just make an image, load it into program then clearcolor the black, probably a lot less trouble.
RE: ICO files
Now I am wondering how an ico image is made. I tried to make one for Sudoku and going On-line to convert the PNG but the shrink always distorted the image beyond recognition. So I am wondering if we can make .ico images with this Editor.
Post by: johnno56 on September 11, 2020, 06:18:39 pm
I'm still getting used to QB64. I thought that _font 8 etc where used for text only screen... Obviously I'm not ready enough of the help file...
Eyedropper was the first word I thought of... In most image editors the colour picker is an eyedropper. If you look in the assets folder there is a toolbox folder within it. I had whipped up a bunch of images to use in stead of using text. After all, most users, expect icons... I suppose I can make them into buttons.... That would take care of any font issues and or text placement. What do you think? I happy to go either way...
I figured the messagebox could be used not only as warning and errors. Oh... maybe a little humour in the messages? Like if you try to draw on the main grid... "Really? Without colour?" (I know. With a default colour this won't apply) It's just an idea. 'normal' messages are so... dull.
Transparencies... I have seen in the past when images were made, a specific colour - usually magenta - was used as the 'transparent' colour. The game editor would set that colour to be transparent. I don't know if QB64 can do that. I know Naalaa and SDLBasic can... Other than that, I have no idea how to achieve transparency, using QB64. That is probably why I chose right mouse click to erase using black. Logic: The mouse pointer is already on the pixel in error. Much more efficient to right click than mouse travel to the erase icon and back and when done mouse travel to change colour and back... Without transparency, right click, for me, works best. But that may change... To achieve transparency, a little mouse travel, could be an acceptable sacrifice...
Icon files. I have no idea as to the difference between ICO and any other image. I know that Linux will use just about 'any' image as a traditional ICO file. eg: When I right click on a Desktop application icon I can examine the 'properties' and can change that application icon to any image type (obviously of similar size) that I want. I can even use one that I made myself. I don't know if Windows can do that, but if it can, then ICO isn't really needed if it can you can use 'any' type of image. If any image can be used then we don't need to convert an ICO file... But, I suppose, we will have to cater for our Windows purists... lol This may help. https://en.wikipedia.org/wiki/ICO_(file_format)
Post by: bplus on September 11, 2020, 06:47:53 pm
Well I have frame and boxes working but a little difficulty getting ellipses symmetric (including circles), no, big problem! ;-))
Yeah, right mouse click way more convenient for erasing. That's easy and might be needed for fixing ellipses.
Post by: johnno56 on September 11, 2020, 07:34:02 pm
I will work on the images. Draw the button and display the image or make the whole button an image? Either way is fine by me...
Hadn't thought of using the right mouse button for anchoring circles and ellipses (and other shapes).... I wasn't sure of getting that far with the editor... lol
Got to go shopping... Maybe back in a hour or so...
Post by: johnno56 on September 11, 2020, 10:02:36 pm
Two sets of images, colour and minimal. Button "selected" images not done yet... If either of these, or if you have any images that you would prefer, let me know? Th finished buttons will have a transparent background.
These we just a simple copy, paste and recolour of the "toolbox" icons... The eyedropper is new.
Post by: bplus on September 11, 2020, 10:23:50 pm
Here I drew a sample of everything over a sample image mostly with Mirror toggled on.
A master piece ;-))
OK @johnno56 back to you for comments :)
Post by: johnno56 on September 11, 2020, 11:24:18 pm
Minor suggestion: You have 'Oval' and 'Oval Fill'... Perhaps, if you prefer text buttons, instead of 'Frame', 'Box' and 'Box Fill'
What did you do to my mushroom? Looks like a rainbow threw up on him... lol
I think our next challenge: Sprite size. 8x8, 16x16 and 32x32... I only wished that I had not lost the early version that had various grid sizes.... The boxes and circles may not work so well on 8x8 and possibly the 16x16... The 8x8 is handy for "old school" games but I won't complain if we leave it out... lol I'm going to go over my discs and archives to at least find a working prototype of grid changes. As you suggested before... there is no point re-inventing the wheel.... I will keep you posted.
Again. Brilliant job!!
Post by: johnno56 on September 11, 2020, 11:33:41 pm
Post by: johnno56 on September 11, 2020, 11:48:33 pm
Post by: johnno56 on September 12, 2020, 01:12:24 am
In the plot() routine the 'size' is hard coded to 10 (64x64). Changed '10's to gsize. Hard coded gsize to 20 and a 32x32 grid was drawn... Hard coded to 40 - 16x16 grid. Coded to 80 - 8x8 grid.
Checked all the tools. Pencil, Line, Frame and Box performed correctly. Ovals (also fill)... Not so much. The other tools took advantage of plot(), which resized exactly, but the ellipses are drawn with the line()-() command. Single sized line. Ovals and filled ovals will still draw on all grid sizes, but because the line is a single thickness, the lines do not match the grid. See attached
The attached was hard coded to a gsize of 40 (16x16)
Another issue are the preview boxes. They also would need 'scaling'. 64x64 and 32x32 seem to be ok. The smaller grids seem to be an issue.
Post by: bplus on September 12, 2020, 12:22:33 pm
Performed an experiment... To draw a grid of 64x64 the gsize is set to 10 (64X10 =gridwidth). Likewise setting gsize to 20 etc etc.
In the plot() routine the 'size' is hard coded to 10 (64x64). Changed '10's to gsize. Hard coded gsize to 20 and a 32x32 grid was drawn... Hard coded to 40 - 16x16 grid. Coded to 80 - 8x8 grid.
Checked all the tools. Pencil, Line, Frame and Box performed correctly. Ovals (also fill)... Not so much. The other tools took advantage of plot(), which resized exactly, but the ellipses are drawn with the line()-() command. Single sized line. Ovals and filled ovals will still draw on all grid sizes, but because the line is a single thickness, the lines do not match the grid. See attached
The attached was hard coded to a gsize of 40 (16x16)
Another issue are the preview boxes. They also would need 'scaling'. 64x64 and 32x32 seem to be ok. The smaller grids seem to be an issue.
Right, I made the drawing tools leaving open the idea we will want to do squares of any size, including n X m rectangles eventually, just wanted to get one set working first. You can fix Plot4Way just as easy as Plot for the circle ellipse tools. I was also thinking with dot tool we could set a radius so we have a perfect circle fill. I don't know if you noticed but ellipse /oval are drawn with 4 pixel = squares center and the left side gets shifted in alignment over a bit from the ellipse drawn while mouse button is down showing general placement of ellipse.
BTW Last night I had a wild and crazy idea, why don't we use Spr Draw to make our drawing tools icons?!?!
Post by: johnno56 on September 12, 2020, 05:37:31 pm
To change the the grid size, either by keyboard or button, would not be practical if one was in the midst of a project. I would dare to suggest that there are two opportunities to change the grid. 1. When the program starts and 2. When "New" is selected. I will the simplest option, keyboard 1 to 4, for 8x8 to 64x64... Sounds like fun...
Use sprdraw to make our own icons... At the moment, as long as the icons were squares, like the ones in the toolbox. No. I don't think that is a crazy idea. Our regular buttons are 80x40, slightly out of the range of the editor, but who said the buttons had to be rectangular? lol To keep similar button spacing, 40x40 could be possible... By changing gsize to 16... Which I just tried and the grid size indeed changed to 40x40... :)
I will re-draw the "buttons", using sprdraw, to 40x40... Of course there will be no transparency... lol Not a big deal at the moment... Seeing the background is black anyway... lol This morning (Sunday) is quite busy for us, so it could be around noon before I can find the time. Just though of another function... 'Move'. When I was creating the last 'screenshot' I would have to draw, erase, redraw the ellipses. It's more of a time saver on larger icons really. Just a thought. Not sure why I thought of that at that particular time... 'Move' isn't important... Just an idea... Must remember the program was initially designed to do pixel art... Sprites and stuff...If we add too much then it becomes a Photoshop wanna-be.... lol Sorry. No coffee yet...
Post by: bplus on September 12, 2020, 07:04:48 pm
What's wrong with buttons at 64X64? Just happens to be the size we have working now. Or do you already have any size working? I mean what's so special about 40?
It is not hard to draw a whole grid of 64x64 or any n X m buttons, have a tool belt that looks like a metal jacket.
hmm... to make draw objects to move around or manipulate, I like!
Oh yeah, for sizing grids just start a standard of loading and saving as "*NXM.png" where N and M are two numbers so we can read the grid size off the filename. Might be a limit to the size M and N though.
Oh and for transparency, we can read something else in file name a color code maybe to set the _CLEARCOLOR to that color and that color will be converted in a little sub so that color will be transparent when used in QB64.
Post by: Dav on September 12, 2020, 08:06:31 pm
- Dav
Post by: johnno56 on September 12, 2020, 09:10:20 pm
Absolutely nothing wrong with 64x64. 40x40 special? Nope. Just the same height as the existing buttons and would not take much to modify their placement. As we don't have too many 'active' buttons at the moment, 64x64 buttons, will work just fine. MSPaint uses small square image buttons. Gimp (and I think Photoshop) uses an 'area' populated with clickable images. We already use rectangular buttons. I will try to make a 'mockup' of an 'area' of images. See the 'area' that Gimp uses... Of course, we do not have as many tools, but it's the idea of the layout...
Post by: johnno56 on September 13, 2020, 12:11:19 am
If you have any ideas on layouts, just let me know, and I'll whip up a new batch....
Post by: bplus on September 13, 2020, 12:16:59 am
You make the call on buttons, I am going to try and get that file retriever to have both lists going at once.
Also do you have doing the different gsizes worked out?
Post by: johnno56 on September 13, 2020, 02:55:04 am
Post by: johnno56 on September 13, 2020, 04:40:18 am
The main grid (10x10) contains a filled 10x10 oval. The main grid is translated to the preview box. The preview box image is the image saved. When the saved image (with the tiny oval in the top left corner) is loaded, it is placed in the preview box and translated back to the main grid. The main grid will display a small oval in the top left corner.
Any ideas?
Post by: bplus on September 13, 2020, 10:41:03 am
I don't mean to harp on this... The attached images will give you an idea of the preview issue.
The main grid (10x10) contains a filled 10x10 oval. The main grid is translated to the preview box. The preview box image is the image saved. When the saved image (with the tiny oval in the top left corner) is loaded, it is placed in the preview box and translated back to the main grid. The main grid will display a small oval in the top left corner.
Any ideas?
Yes, that is why we need to save the the N X M grid size in the file name and offer grid size input when start a new image or loading some part of an image. Then track down every place that uses gsize or 10 for gsize and change all that from const gsize to Dim Shared gSize or 2: gSizeX and gSizeY if you want to graduate from squares.
The trickiest part is tacking a N X M.png onto the end of the filename. I am just saying .png to get one extension going , could be jpg or .bmp. What character will Linux take in file name that we can use to separate Name part from number part $? So it would be "Filename$64x32.png" for a 64 x 32 image grid
Then we can read gSizeX = 64 and gSizeY = 32 and adjust those variables and then draw our grid and run the code from there. So yeah, if we start a new image the file name will have to be setup, thank goodness we have an inputBox sub or function (I forgot).
BTW I don't know well numbers not divisible by 2 will work or if we should mess with different x and y sizes.
I'd say get the buttons nailed down first. I hope to have 2 lists going in file retriever then start on grid size problem.
If you use a grid of buttons, you can tell which one is clicked just like you can tell which grid cell is clicked on the grid, it's just a different grid with different grid sizes.
Post by: bplus on September 13, 2020, 10:43:42 am
Hey, this project is looking pretty neat! I'll be following it. I'm always interested in doodling programs.
- Dav
Thanks Dav, your input welcome! :)
A little reminder, Johnno has Linux and we can't use normal Windows tools for things.
Post by: SMcNeill on September 13, 2020, 12:32:10 pm
Code: QB64: [Select]
The concept here is rather simple: Load any sort of image which you want and work with it inside a fixed 512x512 screen area. (Add a simple set of scroll bars to the side, if you need to see more than that area at any given time.)
The default resolution which we work at is a 32x32 grid area, of 16x16 pixels, for ease of selecting and editing, but it can be easily zoomed in, or zoomed out, as we desire -- to between a 512x512 grid of 1x1 pixels, up to a 1x1 grid of 512x512 pixels. (The demo here showcases the zoom feature, and shows how easy you can implement it.)
All your mouse needs to do is convert any clicks you make upon the grid into coordinates for the original, unscaled image, and then apply your changes there.
Like this, you can easily work with any sort of sprite size, and at various levels of zoomability, to have your editor working with whatever images/sprites, you want to create. ;)
Post by: bplus on September 13, 2020, 02:08:09 pm
If you guys want my simple take on how I'd set this project up and work with it, I'd go with a main layout similar to something like this:Code: QB64: [Select]
The concept here is rather simple: Load any sort of image which you want and work with it inside a fixed 512x512 screen area. (Add a simple set of scroll bars to the side, if you need to see more than that area at any given time.)
The default resolution which we work at is a 32x32 grid area, of 16x16 pixels, for ease of selecting and editing, but it can be easily zoomed in, or zoomed out, as we desire -- to between a 512x512 grid of 1x1 pixels, up to a 1x1 grid of 512x512 pixels. (The demo here showcases the zoom feature, and shows how easy you can implement it.)
All your mouse needs to do is convert any clicks you make upon the grid into coordinates for the original, unscaled image, and then apply your changes there.
Like this, you can easily work with any sort of sprite size, and at various levels of zoomability, to have your editor working with whatever images/sprites, you want to create. ;)
This gives me some ideas to test.
Post by: SMcNeill on September 13, 2020, 06:43:34 pm
This gives me some ideas to test.
Give this little demo a quick test and see if it's not about what you'd be wanting for your sprite editor:
Code: QB64: [Select]
This should work with any image file, but I attached the one I was using. (Which I think was one Cobalt provided for one of his game demos, and I hadn't cleaned it out yet?)
There's no actual selection of anything yet, and I haven't bothered to convert any sort of mousex/mousey input to make it useful, but I think this goes a long ways towards highlighting how I'd work up an image editor with built-in zoomability functionality.
Honestly, I can't imagine any way to work with something like this, any simpler than the above. Our sprite/image is always separate from the main program (EditScreen), so we're not tracking pixels, or an array of information, or anything like that. All we do is convert the coordinates, and the command we want, and we apply it directly to the image in question. When finished, simply save that image with the SaveImage library. :)
Test it out. See if the little demo here isn't doing about what you'd want it to do. Here's to hoping it'll help spark all sorts of nice ideas for you guys to add into your own work-in-progress. ;D
NOTE: As I'm lazy and haven't implemented scrollbars just for a demo, use the arrow keys to navigate around in your image.
Post by: bplus on September 13, 2020, 10:06:27 pm
I was thinking about something like that when loading images to work in the editor. If we can scan over an image at various zoom levels and pickup some section to workup in the editor...
I am in middle of 2nd massive over haul actually making it easier to modify buttons, maybe. With a 512 grid I reduced screen width to 1024, and moved things around and have a ton of room for more buttons. All this could be giant waste of time if I can't rework all the tools to different gSizes, just about getting to that now.
Post by: SMcNeill on September 14, 2020, 02:21:22 am
(No) Blend is a simple toggle which dictates whatto do with an alpha color. When on, your color blends into the background. (RGBA(128,128,128,128) might fade to a light pink while on a deep red background, for example.). When off, the area selected becomes that value, instead.
Replace simply lets you choose a color in the image, and then replace it with another. You could select black, for instance, and with a single click turn it all red.
In combination, the two provide the extremelt useful functionality of letting one choose a 255 alpha black, and transform it into a 255 alpha clear, before saving.
Post by: bplus on September 14, 2020, 01:15:10 pm
Here is Celtic Knot testing at 15X, I attached the 15X Cletic knot file so you can check out it's pixel size :)
Post by: bplus on September 15, 2020, 12:46:50 am
Here is SprDraw v04b3 another overhaul and some refinements, see how you get along without any instructions ;-))
Oops there is a sub folder too, just a sec... OK my tests of 2nd zip look good.