Possible glitch?

Taco Bot · Post by **Taco Bot** » Fri Aug 22, 2014 5:28 am

Ok, so this is what I did:
1) Create a tile.
2) Use the Mark tool to copy the tile.
3) Use the ARROW KEYS to move over to a different tile and enter to select it.

And here's what happened:
1) Instead of the center of the sprite being on the cursor, the bottom right-hand corner is. (Notice the capitalization of "arrow keys", this doesn't seem to occur if I use my mouse to select another tile.)

I don't know if this is a glitch or if it is intentional, but I'm using the August 8th nightly and I find this somewhat annoying.

FnrrfYgmSchnish · Post by **FnrrfYgmSchnish** » Fri Aug 22, 2014 6:07 am

Yeah, I've noticed this for a while now. Workaround is to use the mark tool to grab what you want to copy, then change to a different tool (like draw, line, box, etc.) when switching to the other tile, then back to the clone tool. Switching to another tool doesn't erase the mark tool's selection, but it does prevent this glitch from happening.

The cursor should stay centered correctly if you do it this way--it's only when you go back to the overall view of the tileset while having the clone tool selected that it seems to happen.

EDIT: ...or you can use the mouse apparently. Never knew that. Of course, I pretty much never use the mouse at all for OHR-related stuff, to the point where I might as well just unplug my mouse the moment I open up Custom. XD

Taco Bot · Post by **Taco Bot** » Fri Aug 22, 2014 10:19 pm

FnrrfYgmSchnish wrote:Yeah, I've noticed this for a while now. Workaround is to use the mark tool to grab what you want to copy, then change to a different tool (like draw, line, box, etc.) when switching to the other tile, then back to the clone tool. Switching to another tool doesn't erase the mark tool's selection, but it does prevent this glitch from happening.

The cursor should stay centered correctly if you do it this way--it's only when you go back to the overall view of the tileset while having the clone tool selected that it seems to happen.

EDIT: ...or you can use the mouse apparently. Never knew that. Of course, I pretty much never use the mouse at all for OHR-related stuff, to the point where I might as well just unplug my mouse the moment I open up Custom. XD

I didn't know that this has been going on for so long. If it has, why hasn't James addressed it? I mean, since Beelzebufo he's added an awesome Android settings menu, better palettes, a nicer scripting error system (Thank god), and some other great stuff. Why not just fix this simple yet bothersome glitch?

FnrrfYgmSchnish · Post by **FnrrfYgmSchnish** » Sat Aug 23, 2014 1:12 am

I guess nobody reported it, either because other people use the mouse or because somehow nobody noticed (or they noticed but just didn't report it... whoops.) Or it was one of those "got fixed at one point, then a new change unfixed it" sorts of things.

I dunno, though--I thought for sure that I had mentioned it at least once back when I was in the SlimeSalad IRC channel occasionally, and that's been ages ago...

Post by **Bob the Hamster** » Sat Aug 23, 2014 1:22 am

Huh. This is news to me. I have not seen this myself, and I don't remember anyone mentioning it before now.

I just tried in the current nightly, and I cannot reproduce it.

What version are you guys running? And are you both on Windows?

Pepsi Ranger · Post by **Pepsi Ranger** » Sat Aug 23, 2014 4:15 am

This bug has been around since shortly after Mark/Clone was introduced. If it isn't happening for James, then it's probably a Windows bug. I thought TMC knew about it. It's been mentioned before. I believe it happens anywhere graphics can be edited.

Post by **Bob the Hamster** » Sat Aug 23, 2014 4:27 pm

Does it still happen if you run with the gfx_sdl backend?

custom.exe -gfx sdl

Taco Bot · Post by **Taco Bot** » Sat Aug 23, 2014 5:03 pm

Bob the Hamster wrote:Does it still happen if you run with the gfx_sdl backend?

custom.exe -gfx sdl

The gfx_sdl backend? Sorry, but that term is entirely new to me!

It it's a download, can you post a link?

And if not, can you show me how to access it?

And yes, I'm running Winderz.

Post by **Bob the Hamster** » Sun Aug 24, 2014 2:45 am

Sorry, I guess I didn't make that clear enough. The backend is a built-in thing. You don't need to download it.

Make a shortcut that points to custom.exe

Edit the properties for that shortcut.

Look for the "Target:"

It will be something like:

shortcut target wrote:"C:\blah\blah\blah\custom.exe"

Change it so that it reads:

shortcut target wrote:"C:\blah\blah\blah\custom.exe" -gfx sdl

Notice that the -gfx sdl goes outside the quote marks (if you don't have any quote marks around C:\whatever\custom.exe you do not need to add them)

Run the shortcut, and test the bug again, and let me know if it happens the same way

Taco Bot · Post by **Taco Bot** » Sun Aug 24, 2014 2:52 am

Bob the Hamster wrote:Sorry, I guess I didn't make that clear enough. The backend is a built-in thing. You don't need to download it.

Make a shortcut that points to custom.exe

Edit the properties for that shortcut.

Look for the "Target:"

It will be something like:

shortcut target wrote:"C:\blah\blah\blah\custom.exe"
Change it so that it reads:

shortcut target wrote:"C:\blah\blah\blah\custom.exe" -gfx sdl
Notice that the -gfx sdl goes outside the quote marks (if you don't have any quote marks around C:\whatever\custom.exe you do not need to add them)

Run the shortcut, and test the bug again, and let me know if it happens the same way

Heh. Sorry, not really a computer whiz. I tried that, and strangely enough, the glitch was fixed!

Post by **Bob the Hamster** » Sun Aug 24, 2014 4:05 am

Thanks! That is helpful. This means the bug is in the gfx_directx backend

Post by **TMC** » Sun Aug 24, 2014 4:46 am

gfx_directx has a couple issues related to mouse cursor positioning; this is probably related to that.
http://rpg.hamsterrepublic.com/bugzilla ... cgi?id=988

However in this case I suspect that code somewhere dubiously and unnecessarily using the mouse position as stored state could be just as easily blamed.