Right-click to fill doesn't do anything (at least, not visibly).

I think it might just be a little confusing. When editing height, it will fill the currently selected height you are "drawing". But for the other flags you are toggling the state, so there is no inherent value being "drawn". So for those it fills based on the value of the minitile you right clicked. I might change it to fill with the opposite of the value you right clicked on, that might be a little more intuitive, at least in that case right clicking would always change something visibly.

Oh, that's how it works! Alright, that seems to work fine. Thanks!

edit: after some mucking about in the program, I think that making right-click fill the opposite for binary properties (walkability, ramp, block vision, etc) would be a great change, so basically what you mentioned in the post I quoted. As for the hotkeys to apply to properties, I think these are useful but it might be even more ideal to just axe the dropdown menu altogether and separate the single property and all properties functions into different buttons that are permanently affixed to the UI, like so:



Request/bug? -> PyMPQ: 'Delete' hotkey for deleting files? Isn't working on my end, not sure if it's supposed to. edit: actually it's something one of us reported earlier

edit 2: had a brief look at the GitHub issues for PyMS, if there's anything I can do to resolve any of these let me know and I'll give you whatever info I can. I know it's not a weekend job but it'd be awesome to knock down that number of open issues.

Post has been edited 4 time(s), last time on Sep 12 2017, 10:03 pm by Pr0nogo.

Done. Didn't bump the version number, just update.

I don't really want to fill the UI like that. The intention is if you are doing complex and repetitive things like that you should use the settings importer, and otherwise the keyboard shortcuts.

Yeah I have an issue for that. I looked into it before and was not able to figure it out at the time, then forgot about it.

There are not many things that will help other then me getting more time to put into it The only ones I can think of off the top of my head would be the tickets labeled as documentation, but those won't help getting features/bugs completed

Thanks!

To this end, is there documentation on what each 'reuse megatile/minitile' setting does in the import window? I had them all unticked so I could import visually identical tiles and modify minitile properties on a mega-by-mega basis, but I have no idea what does what here, really.

Right. Doing tutorials is something voy's already up to, and I have plans to make them in the future. I'll let you know when I wind up contributing in any capacity.

Bug? -> PyTILE: Shift+click/Ctrl+click doesn't seem to do anything in the group selector. Unless that update only affected the .bmp selector during the import process?

Megatile groups have basic settings (everything outside the Megatile editor), and just point to the megatiles. Megatiles are a bunch of settings flags for each minitle in the megatile, and just points to mintiles. Minitiles are just images. You should pretty much always reuse duplicates for minitiles, there are very few reasons not to. But for megatiles its very important whether you reuse duplicates or not. If multiple megatile groups are referencing the same megatile, editing the megatile will affect all of those groups, not just the group you have selected. This can be very useful, or very problematic, depending on how you are using your tiles. The Old and New allow you to differentiate between the old (existing) tiles and the new (imported) tiles. So you might want to reuse duplicate dirt tiles in your import, but not reuse the dirt tile that exists in the tileset already, so you can edit your new megatile settings without worry you might affect the original dirt tiles.

Sounds good.

I'm not exactly sure what you mean by 'group selector' or '.bmp selector'. The shift+click/ctrl+click is for the Palette windows, the main window can only edit one group/megatile at once.

Post has been edited 1 time(s), last time on Sep 13 2017, 4:48 am by poiuy_qwert.

Ah, gotcha. So tick the 'new' reuse and keep 'old' unticked if this is the desired outcome? Thanks for the writeup.

Yeah, in the group palette window, clicking anywhere adds the group you've clicked to your selection (similar to iscript entries in PyICE). Shift/Ctrl doesn't actually do anything different in this case. I was expecting to be able to click row 1, hold shift, and click row 10, and select all rows in between, but that does not occur.

Bugs -> PyBIN:
The up arrow moves the selection down in the list, and the down arrow moves the selection up in the list.
With one item selected, shift-clicking on the list will move the selection up or down.
PyBIN will not track if you've saved or not and will not warn you if you've made changes and attempt to exit the program without saving.

It all depends on what you want to do for your specific cases, so yeah choose what you want for your desired outcome.

That is definitely not how it should work, I can not reproduce it doing that, and I don't see how it could do that based on the code. Are you sure you have updated to the latest version? Are you sure we are talking about the same window, could you take a screenshot just to confirm? Or would it be possible for you to take a video of the issue in action? I also have a couple things you could try for me, open PyTILE.pyw and change:
1) Go to line 1165 and add a log right above it so it looks like:

2) Go to line 1123 and add a debug logger right above it so it looks like:

3) Try adding a # to line 1117 so it is commented out, like:

After doing that open PyTILE, open the group palette, and execute certain selections in a specific order and write down exactly what you did, like: 1) left click id 0, 2) shift+click id 10, 3) ctrl+click id 5, etc.
Once you have closed PyTILE, send me your PyTILE log and the steps you wrote down, I can hopefully correlate the log with your steps and get a better idea of whats happening on your side.

Noted.

I don't know what you mean, you will need to be more specific.

Noted.

Thanks!

Video of PyTILE bug. First couple clicks are normal, with nothing held. Second is with shift and sometimes ctrl held. No change.

Doing that fixed the problems and the program appears to behave as intended, which doesn't really make sense to me unless the culprit was what I commented out.

Video of PyBIN bug. I attempt to shift+click to select multiple elements (for moving them up or down, or mass deleting, etc.) and it just moves the selection in the list instead.

Yeah, that line you commented out was the only thing I could see causing the issue. I started adding the "Command-Button-1" bindings in addition to "Control-Button-1" in some places because it is more convenient for mac users, but it looks like windows does not like that. Well at least its an easy solve.

Thanks, that clears it up. It looks like it thinks you are doing a drag and drop for some reason. I'll look into it.

Thanks!

Issue with all programs in PyMS in general: Mousing over the buttons at the top doesn't show their tooltips; update/reinstall didn't help :v
(I know that's not a 'global' issue, but I can't figure it out myself)

Hmm I changed stuff about how that works recently, it seems to be working fine for me on Mac. Might be a windows issue, so it could be hard for me to fix I have created an issue for it.

PyAI or PyDAT feature request: Have something in PyAI show unit force value (Mousing over units?) or add a box to PyDAT units.dat that shows it - formula to calculate it (courtesy of our resident Jesus, Neiv) below

Force = (sqrt((range / cooldown) * factor * damage + (((factor * damage * 2048) / cooldown) * (hp + shields)) / 256) * 7.58) * unit_specific_reduction
Unit specific reductions:
- Workers get 25% of default
- Interceptors, scarabs, mines 0%
- Firebats, mutalisks, zealots 200%
- Defilers, inf. terrans 1/16
- Reavers 10%
(100% for all other units)
Factors are weapon factors from weapons.dat
All divisions and the 7.58 multiplication are rounded down to integers, square root is not rounded down.

Unrelated -
The lack of tooltips when mousing over buttons (notably command tooltips in PyAI work fine) also happens for Pr0nogo, so its probably a global windows issue now

Unrelated 2x -
Trying to save an MPQ when SCMD (or anything else) holds onto it crashes PyMPQ, should probably just show an error and let you go back instead

Post has been edited 1 time(s), last time on Oct 3 2017, 9:00 pm by Nekron.

I'll probably add this to PyDAT first, not sure how I would implement it in PyAI.

It should be fixed now.

It should not crash, it should just present an error. If you can provide a crash log I can look into it.

Thanks

Well, I guess it does present an error, it doesn't "crash" as in "closes immediately with no notice", but it still closes after you okay away the error when it (I would think) doesn't have to

I figure you know what the error would be, i'll include it here anyway just in case https://pastebin.com/raw/XLbQMt17

it's more than enough if you just implement the force values into PyDAT, PyMS is not too resource intensive anyway so I can afford to have both PyAI and PyDAT open at once xD
Thanks for fixing the tooltips!

Post has been edited 1 time(s), last time on Oct 5 2017, 2:23 pm by Nekron.

https://pastebin.com/raw/J7b4iBFU trying to save a bwscript with this script in crashes PyAI with the following error message
the script is probably fucked, but well, I assume that crashing shouldn't be the correct answer anyway, especially if the editor lets me save it
edit: now I literally can't save anything LMAO/works after redownloading

Post has been edited 2 time(s), last time on Oct 22 2017, 11:39 am by Nekron.

This warning should not show up - if the AI owns at least 2 expansions + random_jump will not fire (1/2 chance) the command will be executed. I don't understand why it wouldn't, anyway.

PyGRP:

1. When shift + clicking a frame groups, when importing them frames, the last frame you click (supposedly the very last frame) it ends up being frame 0 in PyGRP

2. Also, while pressing "home" keyboard key does take you to frame 0, pressing "end" keyboard key takes you to the frame before last

EDIT: issue #1 happens regardless of how I select my range of frames

Selecting frames from last to first solved the issue for me, though obviously it isn't very intuitive.

That is undesired behaviour, though, as it is still an issue and that is just a temporary bodge. But thanks.

In my case I just deleted and reimported the frame.