Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Vic Romano]

Even though I know what this is, every time I see this thread I imagine a fortress with mice in it.  Too much Redwall as a child. Thank you for your time.

[Shukaro]

Alright, uploaded a new version, 1.2c for 34.06.

Tons of bug fixes in this one, so most issues should be fixed. I'm still looking into the tracking detection issue, so in the meantime simply reload the script (Ctrl + r by default) to fix it. Enjoy!

[Noffie]

Does this work with alternate tiles or graphics?

[Shukaro]

Does this work with alternate tiles or graphics?

Yep, it's fully compatible with any tileset or graphics pack that you'd like to use. 

E: I'll have an updated version for 34.07 out sometime tomorrow as well.

[Shukaro]

Heyo, updated version for 34.07 is now live! 

[Rybec]

Just a quick question: The cursor controls are always really zippy, unless it needs to move diagonally. Why doesn't the script shift-move diagonally like it does orthogonally? Or even just jump quickly on an orthogonal to close the distance faster?

[vonduus]

Great utility, just what I always hoped for ever since I started playing DF, thanks a lot.

Minor bug: Workshops did not show up in the menu, so I had to change a line in menus.txt:

Instead of "Workshops|g(Buildings)" I wrote "Workshops|Buildings" and now everything seems to work as intended.

I was unsure if I should retain the original line, but I decided that it probably was a meaningless command, a sort of mental typo on the developerīs part (as I believe it can be translated into "go to in-game Building-menu", and DF has no Building-menu (but MouseFort has)), so I left it out. Hope I didnīt break anything, I have no programming skills whatsoever .

[vonduus]

Another minor bug/glitch/unintended complication: Somehow ( ) I accidentally triggered the zoom with my mousewheel to a very, very far out zoom, and it seems I canīt access this function again to zoom back in, unless I quit the script.

I tried to add two new lines to the keys.txt file, to trigger the default DF MouseWheel command with a ctrl-command, like:

^Wheelup|k{Wheelup}
^Wheeldown|k{Wheeldown}

but it didnīt work. I also tried to leave the "k" out, as a wheelup probably isnt a key (?), but to no avail.

I guess the script does not understand the term {Wheelup}, or perhaps it needs another function trigger instead of "k", but as I said, I am no programmer, and have no idea what I am talking about. Nevertheless, I have already added some more valuable DFHack functions to my script, like copystock and some watch functions, and I really would like to be able also to define some more functions for my mouse.

What shall I write on the right side of the vertical line, to make the script understand that when I use ctrl-Wheelup/down I want the script to do a default Wheelup/down, ie. a zoom?

edit: I checked the syntax and found out that I had left out some "("s and ")"s. The following string makes the game zoom on Ctrl-Mousewheel(up/down):

^Wheelup|k({Wheelup})
^Wheeldown|k({Wheeldown})

[vonduus]

Two more question:

How do I install the non-compiled scripts to try them out?

And after installing them, how do I figure out what they actually do? Do they show up in the menu?

Reading the said files gave me no clues whatsoever, not being a programmer and all that. Reading the tutorials on the AHK site just made me even more confused. Please, help. I apologize for being so stupid

edit: Okay, now I understand, the uncompiled scripts are provided for inspection - sorry again for being stupid.



PS I just found an old post i made on this forum back in 2010:

Quote: "I wish someone with programming skills (and I believe quite a few DF-players are programmers) would create some kind of consistent interface on top of the existing interface, so that you could input orders with the mouse from a menu and place structures on the map with the mouse (or something). I have no programming skills so I don't know if this is at all possible."

Thanks again, Shukaro!!!!

[Shukaro]

Sorry about the delay in responding, I've been pretty busy lately. (And the forum decided not to notify me about the new posts for some reason)

Just a quick question: The cursor controls are always really zippy, unless it needs to move diagonally. Why doesn't the script shift-move diagonally like it does orthogonally? Or even just jump quickly on an orthogonal to close the distance faster?

The reason why it can't shift-move diagonally is because the game only seems to support shift-moving with the arrow keys. I'll see if it's faster if I omit the diagonal movement, though.

Great utility, just what I always hoped for ever since I started playing DF, thanks a lot.

Minor bug: Workshops did not show up in the menu, so I had to change a line in menus.txt:

Instead of "Workshops|g(Buildings)" I wrote "Workshops|Buildings" and now everything seems to work as intended.

I was unsure if I should retain the original line, but I decided that it probably was a meaningless command, a sort of mental typo on the developerīs part (as I believe it can be translated into "go to in-game Building-menu", and DF has no Building-menu (but MouseFort has)), so I left it out. Hope I didnīt break anything, I have no programming skills whatsoever .

Yeah, that looks like it was just a typo on my part  , I'll be sure to fix it for the next release.

Another minor bug/glitch/unintended complication: Somehow ( ) I accidentally triggered the zoom with my mousewheel to a very, very far out zoom, and it seems I canīt access this function again to zoom back in, unless I quit the script.

I tried to add two new lines to the keys.txt file, to trigger the default DF MouseWheel command with a ctrl-command, like:

^Wheelup|k{Wheelup}
^Wheeldown|k{Wheeldown}

but it didnīt work. I also tried to leave the "k" out, as a wheelup probably isnt a key (?), but to no avail.

I guess the script does not understand the term {Wheelup}, or perhaps it needs another function trigger instead of "k", but as I said, I am no programmer, and have no idea what I am talking about. Nevertheless, I have already added some more valuable DFHack functions to my script, like copystock and some watch functions, and I really would like to be able also to define some more functions for my mouse.

What shall I write on the right side of the vertical line, to make the script understand that when I use ctrl-Wheelup/down I want the script to do a default Wheelup/down, ie. a zoom?

edit: I checked the syntax and found out that I had left out some "("s and ")"s. The following string makes the game zoom on Ctrl-Mousewheel(up/down):

^Wheelup|k({Wheelup})
^Wheeldown|k({Wheeldown})

Ah, that looks like something I'll have to add in. I usually don't zoom, so I forgot you could do that. The {} just denote a key name, without those it would send each letter, so the syntax for sending keys is a bit different in that way from the hotkey syntax.

Two more question:

How do I install the non-compiled scripts to try them out?

And after installing them, how do I figure out what they actually do? Do they show up in the menu?

Reading the said files gave me no clues whatsoever, not being a programmer and all that. Reading the tutorials on the AHK site just made me even more confused. Please, help. I apologize for being so stupid

edit: Okay, now I understand, the uncompiled scripts are provided for inspection - sorry again for being stupid.



PS I just found an old post i made on this forum back in 2010:

Quote: "I wish someone with programming skills (and I believe quite a few DF-players are programmers) would create some kind of consistent interface on top of the existing interface, so that you could input orders with the mouse from a menu and place structures on the map with the mouse (or something). I have no programming skills so I don't know if this is at all possible."

Thanks again, Shukaro!!!!

The uncompiled scripts are just there in so that people can look through them if they want to see how it works, the actual running script always references the compiled ones. If you have any questions about the script, feel free to ask! Hehe, yeah, the main reason I made this is because I always thought that DF could be improved by adding actual mouse support.

[vonduus]

I have both the cursor tracking and the forced tray problem on my Win7-64.

Some scientific facts:

Set-up: DF in full screen mode.
The cursor tracking is definitely working in all sub-modes like view, look, designate etc.
Right-clicking immediately sends DF to tray

Set-up: DF in windowed mode.
Cursor tracking does not work. Toggling tracking off and then on does not help. Reloading the script does not help. Reloading the game does not help.
Right-clicking is definitely working, all my new menu items are accessible and working as intended.

Field reports, difficult to reproduce:
Sometimes mouse-tracking works in windowed mode. I have seen it perhaps five or six times over the last few days. Most of the times I have no idea why it suddenly worked.
Twice I have seen it begin to work after clicking the button that resizes the DF window (the button between the minimize and close buttons in the top right corner of the windows frame). My window filled the whole screen, then I clicked the resize button (and had DF in a smaller than full size window), and immediately clicked it again for full screen, and suddenly mouse tracking worked. Another time I accidentally hit the resize button instead of the tray button and noticed that the window did a very slight adjust (indicating it was almost but not wholly full size before I clicked the button), and voila: Mouse-tracking. Unfortunately I have not been able to reproduce this.
Both times I later shifted to some other program that was open in the background (DFHack and Firefox resp.) and when I came back to DF, mouse tracking was irretrievably gone, no matter how much resizing I did.

Finding:

It is possible to go to full screen mode to benefit from the mouse tracking (to find a spot or a dorf or some interesting stone, fx), then push F11 to go to windowed mode to use the menu (select a building or a task), then push F11 again to go back to full screen mouse-tracking, (to place the building or designate the dig field).

This is a bit inconvenient as a work-around. And it is difficult to automate, because how can the script know that I intend to right-click (so as to press a virtual F11 before I do so) before I actually right-click, and then it is too late, because DF is in the tray?

Shukaro, how do you track the mouse? I tried to read the scripts, and I figured out that when first the script knows where the mouse is, it just uses virtual arrow-keys to get there. But how does it detect the position of the cursor? Is it measuring it  from the top-left corner of the screen? And why does it detect this correctly (and every time!) in full-screen mode and not in windowed mode?  The only difference I can think of is that the top-left corner has moved a little bit inward and a little bit more downward to free up space for the win7 window frame. Is this displacement the same across all screen sizes?

If this cannot be fixed for full screen DF, then so be it, I am biased here, always play in windowed mode. But I believe there must be a fix for windowed mode, because mouse-tracking  has worked for me several times in that mode. I believe it is a question of customizing the script to allow for my screen size. Perhaps I am wrong, I am no programmer and all that.

STOP PRESS:

If I grab the DF window and move it slightly upwards and to the left, so that its top and left borders actually disappear out of the screen, then mouse tracking works. This is fully reproducible.

[Shukaro]

I have both the cursor tracking and the forced tray problem on my Win7-64.

Some scientific facts:

Set-up: DF in full screen mode.
The cursor tracking is definitely working in all sub-modes like view, look, designate etc.
Right-clicking immediately sends DF to tray

Set-up: DF in windowed mode.
Cursor tracking does not work. Toggling tracking off and then on does not help. Reloading the script does not help. Reloading the game does not help.
Right-clicking is definitely working, all my new menu items are accessible and working as intended.

Field reports, difficult to reproduce:
Sometimes mouse-tracking works in windowed mode. I have seen it perhaps five or six times over the last few days. Most of the times I have no idea why it suddenly worked.
Twice I have seen it begin to work after clicking the button that resizes the DF window (the button between the minimize and close buttons in the top right corner of the windows frame). My window filled the whole screen, then I clicked the resize button (and had DF in a smaller than full size window), and immediately clicked it again for full screen, and suddenly mouse tracking worked. Another time I accidentally hit the resize button instead of the tray button and noticed that the window did a very slight adjust (indicating it was almost but not wholly full size before I clicked the button), and voila: Mouse-tracking. Unfortunately I have not been able to reproduce this.
Both times I later shifted to some other program that was open in the background (DFHack and Firefox resp.) and when I came back to DF, mouse tracking was irretrievably gone, no matter how much resizing I did.

Finding:

It is possible to go to full screen mode to benefit from the mouse tracking (to find a spot or a dorf or some interesting stone, fx), then push F11 to go to windowed mode to use the menu (select a building or a task), then push F11 again to go back to full screen mouse-tracking, (to place the building or designate the dig field).

This is a bit inconvenient as a work-around. And it is difficult to automate, because how can the script know that I intend to right-click (so as to press a virtual F11 before I do so) before I actually right-click, and then it is too late, because DF is in the tray?

Shukaro, how do you track the mouse? I tried to read the scripts, and I figured out that when first the script knows where the mouse is, it just uses virtual arrow-keys to get there. But how does it detect the position of the cursor? Is it measuring it  from the top-left corner of the screen? And why does it detect this correctly (and every time!) in full-screen mode and not in windowed mode?  The only difference I can think of is that the top-left corner has moved a little bit inward and a little bit more downward to free up space for the win7 window frame. Is this displacement the same across all screen sizes?

If this cannot be fixed for full screen DF, then so be it, I am biased here, always play in windowed mode. But I believe there must be a fix for windowed mode, because mouse-tracking  has worked for me several times in that mode. I believe it is a question of customizing the script to allow for my screen size. Perhaps I am wrong, I am no programmer and all that.

STOP PRESS:

If I grab the DF window and move it slightly upwards and to the left, so that its top and left borders actually disappear out of the screen, then mouse tracking works. This is fully reproducible.

Well, the issue of the menu not working in full-screen mode is known. It's caused by the fact when DF is in full-screen control it takes control of on-screen rendering, much like any other full-screen game, then when the script tries to bring the menu up, DF loses focus. That's just a thing with windows, sadly. The issue is usually trivial to fix, but DF doesn't play nice with being resized and having its styles changed, so unless that issue is addressed, menus in full-screen mode won't work. 

As for the mouse tracking issue, I'll have to ask you to do a few things for me so I can get some more information, if you don't mind. Mouse Fortress reads DFs memory for any data it needs for speed, reliability, and ease-of-coding, and I use Cheat Engine to find anything I need in DFs memory, so the next time the mouse tracking stops working I'd like you to take the following steps:

• Confirm the menu is working
• Reload the script (Make sure you get the traytips at the bottom right)
• Open the task manager and look for mouse.ahk, cursor.exe, and watch.exe
• Open cheat engine and connect to DF
• Load this table up
• Upload a screenshot of all the values CE displays

I'd also like to view your menus.txt, keys.txt, and config.ini from your mouse folder

[vonduus]

Last things first: Here are my menus.txt, keys.txt (both modified) and config.ini (unmodified, I believe)

Spoiler (click to show/hide)

Look|Info|g(k)
View|Info|g(v)
View Building|Info|g(t)
Info
Dig|Designate|g(dd)
Fell Trees|Designate|g(dt)
Gather Plants|Designate|g(dp)
Smooth|Carve|g(ds)
Engrave|Carve|g(de)
Carve Fort|Carve|g(da)
Carve|Designate
Up|Stairs|g(du)
Down|Stairs|g(dj)
Up/Down|Stairs|g(di)
Ramp|Stairs|g(dr)
Remove|Stairs|g(dz)
Stairs|Designate
Channel|Designate|g(dh)
Remove Designation|Designate|g(dx)
Remove Construction|Designate|g(dn)
Remove Building|Designate|g(qx)
Designate
Armor Stand|Furniture|g(ba)
Bed|Furniture|g(bb)
Seat|Furniture|g(bc)
Burial Receptacle|Furniture|g(bn)
Cabinet|Furniture|g(bf)
Container|Furniture|g(bh)
Weapon Rack|Furniture|g(br)
Statue|Furniture|g(bs)
Slab|Furniture|g(b!s)
Table|Furniture|g(bt)
Archery Target|Furniture|g(bA)
Traction Bench|Furniture|g(bR)
Nest Box|Furniture|g(bN)
Hive|Furniture|g(b!h)
Furniture|Buildings
Wall Grate|Constructions|g(bW)
Floor Grate|Constructions|g(bG)
Vertical Bars|Constructions|g(bB)
Floor Bars|Constructions|g(b!b)
Paved Road|Constructions|g(bo)
Dirt Road|Constructions|g(bO)
Glass Window|Constructions|g(by)
Gem Window|Constructions|g(bY)
Wall|Structures|g(bCw)
Floor|Structures|g(bCf)
Ramp|Structures|g(bCr)
Up Stair|Structures|g(bCu)
Down Stair|Structures|g(bCd)
Up/Down Stair|Structures|g(bCx)
Fortification|Structures|g(bCF)
Structures|Constructions
Constructions|Buildings
Kennels|Workshops|g(bk)
Farm Plot|Workshops|g(bp)
Leather Works|Workshops|g(bwe)
Quern|Workshops|g(bwq)
Millstone|Workshops|g(bwM)
Loom|Workshops|g(bwo)
Clothier's Shop|Workshops|g(bwk)
Bowyer's Workshop|Workshops|g(bwb)
Carpenter's Workshop|Workshops|g(bwc)
Metalsmith's Forge|Workshops|g(bwf)
Jeweler's Workshop|Workshops|g(bwj)
Mason's Workshop|Workshops|g(bwm)
Butcher's Shop|Workshops|g(bwu)
Tanner's Shop|Workshops|g(bwn)
Craftsdwarf's Workshop|Workshops|g(bwr)
Siege Workshop|Workshops|g(bws)
Mechanic's Workshop|Workshops|g(bwt)
Still|Workshops|g(bwl)
Farmer's Workshop|Workshops|g(bww)
Kitchen|Workshops|g(bwz)
Fishery|Workshops|g(bwh)
Ashery|Workshops|g(bwy)
Dyer's Shop|Workshops|g(bwd)
Soap Maker's Workshop|Workshops|g(bwS)
Screw Press|Workshops|g(bwp)
Wood Furnace|Workshops|g(bew)
Smelter|Workshops|g(bes)
Glass Furnace|Workshops|g(beg)
Kiln|Workshops|g(bek)
Trade Depot|Workshops|g(bD)
Workshops|Buildings
Door|Mechanisms|g(bd)
Floodgate|Mechanisms|g(bx)
Floor Hatch|Mechanisms|g(bH)
Bridge|Mechanisms|g(bg)
Well|Mechanisms|g(bl)
Ballista|Mechanisms|g(bib)
Catapult|Mechanisms|g(bic)
Stone-Fall Trap|TrapsMachines|g(bTs)
Weapon Trap|TrapsMachines|g(bTw)
Lever|TrapsMachines|g(bTl)
Pressure Plate|TrapsMachines|g(bTp)
Cage Trap|TrapsMachines|g(bTc)
Upright Spear/Spike|TrapsMachines|g(bTS)
Screw Pump|TrapsMachines|g(bMs)
Water Wheel|TrapsMachines|g(bMw)
Windmill|TrapsMachines|g(bMm)
Gear Assembly|TrapsMachines|g(bMg)
Horizontal Axle|TrapsMachines|g(bMh)
Vertical Axle|TrapsMachines|g(bMv)
Support|TrapsMachines|g(bS)
Animal Trap|TrapsMachines|g(bm)
Restraint|TrapsMachines|g(bv)
Cage|TrapsMachines|g(bj)
Traps/Machines|Mechanisms
Mechanisms|Buildings
Buildings
Animal|Stockpiles|g(pa)
Food|Stockpiles|g(pf)
Furniture|Stockpiles|g(pu)
Corpses|Stockpiles|g(py)
Refuse|Stockpiles|g(pr)
Stone|Stockpiles|g(ps)
Wood|Stockpiles|g(pw)
Gem|Stockpiles|g(pe)
Bar/Block|Stockpiles|g(pb)
Cloth|Stockpiles|g(ph)
Leather|Stockpiles|g(pl)
Ammo|Stockpiles|g(pz)
Coins|Stockpiles|g(pn)
Finished Goods|Stockpiles|g(pg)
Weapons|Stockpiles|g(pp)
Armor|Stockpiles|g(pd)
Custom|Stockpiles|g(pc)
Custom Settings|Stockpiles|g(pt)
Remove|Stockpiles|g(px)
Stockpiles
|
Set Prefs||g(q)
|
Prospect|DFHack|a(prospect)
Clean All|DFHack|a(clean all)
Confiscate Junk|DFHack|a(cleanowned scattered)
Vein Dig|DFHack|a(vdigx)
Follow Unit|DFHack|a(follow)
Stonesense|DFHack|a(stonesense)
Copystock|DFHack|a(copystock)
DFHack
|
Refresh Script||l
Exit Script||s

Spoiler (click to show/hide)

RButton|m
~MButton|d
+~MButton|pan
+LButton|k({Enter})
+RButton|k({Escape})
Wheelup|k(>)
Wheeldown|k(<)
+Wheelup|k(-)
+Wheeldown|k({+})
^Wheelup|k({Wheelup})
^Wheeldown|k({Wheeldown})
!r|ru(t)
!q|q
^r|l
^v|a(vdigx)
^f|a(follow)
^+q|s
F9|g(z{Right}{Right}{Right}{Enter})
F10|g(z{Enter})

Spoiler (click to show/hide)

[settings]
[offsets]
; Base address of DF. Don't change unless you need to.
base=0x0400000
; Offsets for various stuff. Again, don't change unless you need to.
cursorx=0x85A848
cursory=0x85A84C
windowx=0xBD78CC
windowy=0xC05AD8
mousex=0x85B0FC
mousey=0x85B100
sidemenutype=0x121D250
pause=0x1213754
constructioncursor=0x1571638
fullmenu=0x1429AF4
zlevel=0xC05AB0
windowsizex=0x85ADB0
windowsizey=0x85ADB8
mapsizex=0x142D4EC
mapsizey=0x142D4F0
[pass]
; This section is only for the script's use, don't touch please.
dragkey=~MButton
menucount=145
keycount=19
cursoron=1
ruleon=0
flagvar=t

I am downloading Cheat Engine.

[vonduus]

It is a funny world. I thought I could very easily make your script not work again, but no such luck. I resized my windows, I quit and restarted DF, but cursor tracking has apparently come to stay. Instead the link to DFHack seems to be broken: When I send the stonesense command (or any other) through the menu, nothing happens.

So I tried out the Cheat Engine to see if I could figure out how to use it, and I believe I can. I am not supposed to push the scan button? Just upload a pic of the data in the bottom half of Cheat Engine?

Btw,   the data I got now from Cheat Engine is about cursor, window and mouse position, so I guess it is of no help to you with respect to the new DFHack issue, so I'll wait before I upload anything.

Is it at all possible to upload pictures here?

[vonduus]

This is with cursor tracking in working order and DFHack not working.

cheat data

Just testing, seems it works.