Is anyone using AC on Windows 7? One of my translators is having a weird behavior where large hit area targets are appearing out of nowhere and I'm not able to repro it. I had him send me a screen capture and the only thing I see that's different between our setups is that he's on Win7 and I'm on Win10. I wouldn't expect that to matter, but it's been a long time since I had a Win7 box to try it on.

That sounds suspiciously like the "double-clicking a file in an OpenDialog or SaveDialog causing a mouse-up event to bleed to the image-area resulting in the addition of an extra area spanning from the top-left corner" issue. Wayback, I've sent you a possible workaround for it and a link to a video showing how to reproduce it. No relation to Windows version, still happens to me on Win10.User-level workaround: do not double click files in the open dialog to open them, select the file and click on the "Open" button instead.

Interesting. I had completely forgotten about that. It made large red squares, not tiny ones, didn't it? I thought I effectively made the problem go away when I started clearing the tiny squares, but if it made large ones, that would explain a lot. Let me follow up with Marco.

Okay, I've got the UI for localization in a place I'm comfortable with it now. I may add a thing here or there, but the highest bang for the buck is working.

I'm starting to reconsider my stance on individual files vs one large js. I've got RfJ with 3 languages now, and, while it works fine, unzipping 4500 small htms is taking longer than I'd like. As I consider adding 3 or 4 more languages, it's probably going to get unwieldy. I'll spend some time finding the right balance between understandability/readability and functionality, but I'm exploring it a little.

Two other features I'm thinking about but not actively working on yet are conditional hit targets (inspired by WBA) and exportable save states. I haven't thought too much about either of those yet, though.

tlaero wrote:Two other features I'm thinking about but not actively working on yet are conditional hit targets (inspired by WBA) and exportable save states. I haven't thought too much about either of those yet, though.

It would be something along the lines of a new text box in the Areas that lets you provide a function. If the function returns true, the hit target shows. If it returns false, the hit target doesn't show. So you could have a book sitting on the table and a hit target that says "pick up the book." And you'd have a function that returns true if the book is there or false if it's already been picked up. If it's been picked up, the hit target wouldn't show. If it's not, it would. Kind of the next step after having the book show or not in RfJ.

I played "The Division" for the last few days, but the servers went down today, so I implemented condition functions for hit targets in AC. I'll test it a bit more before uploading, which may not be until the weekend depending on how long Ubisoft takes to fix their servers. Basic gist is that there's a "condition function" box in the area data bar now. If you put the name of a function in it, and that function returns true, the hit target will be added to the page. If it returns false, it won't be.