Recent Posts

Pages: [1] 2 3 ... 10
1
WeiDU / Re: DECOMPRESS_BIFF fails to find the file
« Last post by Wisp on March 27, 2017, 11:35:54 AM »
Can you check for lines like "Possible HD/CD Path:" in your debug? Also which ini files are loaded before these lines are printed, if they are. It looks like it might be raising an exception while reading the ini file and resorting to default paths. If you have lines like the aforementioned in your debug (and they correspond to what you have in your ini), at least it's not that.
2
WeiDU / Re: Roadmap
« Last post by qwertyqwerty on March 26, 2017, 01:22:15 PM »
That is great, I've been thinking similarly for a long time, tried to start, but Qt takes time to learn.
However, I don't think that simply adding GUI is going to change much at this point. There's BWS already, and for large installations it's simply integral. For small ones, it's not too hard to run setup-mymod a few times.
But, a native replacement for BWS, with proper UI and more functions, would be the holy grail.
3
WeiDU / Re: Move + symlink fails
« Last post by qwertyqwerty on March 26, 2017, 01:03:13 PM »
The code is generalized_biffing mod, I just run a second instance to really empty override.
I have it some more testing, and symlink doesn't fail the installation by itself, I tried to move the dir inside game folder and link to it, it worked fine. But I can reliably reproduce it when linking to original placement.

Anyway, it's a minor issue, so probably not worth your time.
4
WeiDU / Re: DECOMPRESS_BIFF fails to find the file
« Last post by qwertyqwerty on March 26, 2017, 12:41:35 PM »
I have no "data" in my paths at all:
Code: [Select]
HD0:=/Users/adm/bg2/
CD1:=/Users/adm/bg2/
CD2:=/Users/adm/bg2/
CD3:=/Users/adm/bg2/
CD4:=/Users/adm/bg2/
CD5:=/Users/adm/bg2/
CD6:=/Users/adm/bg2/

Relevant debug part:
Code: [Select]
[baldur.ini] loaded, 3989 bytes

HD0: is /Users/adm/bg2/
Looking for biff 25ambsnd.bif at CD6/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at CD5/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at CD4/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at CD3/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at CD2/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at CD1/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at CD6/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at CD5/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at CD4/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at CD3/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at CD2/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at CD1/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at ./CD1/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at ./CD2/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at ./CD3/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at ./CD4/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at ./CD5/data/25ambsnd.bif
Looking for biff 25ambsnd.bif at ./CD6/data/25ambsnd.bif
Stopping installation because of error.
I've no idea why is it looking there.
5
WeiDU / Re: Graphical frontend
« Last post by Wisp on March 25, 2017, 04:47:45 PM »
Now the component-selection view looks a bit like this: link. FORCED_SUBCOMPONENTs are handled by having the first subcomponent starting out already selected and making it impossible to deselect all subcomponents in the grouping. I shall hold off on introducing GROUPs, in favour of putting a Select-All tristate checkbox up by the Components label. AL|EN's concerns have been addressed by popping up the something-is-a-happening window that is used for component-installations for uninstallations, as well. It is also not possible to close it while things are a-happening.

Now I'm off to tame the wild beast of component requirements. I may have to resort to boolean algebra. If you don't hear from me within a month, I have most likely perished in the attempt.
6
WeiDU / Re: Graphical frontend
« Last post by AL|EN on March 19, 2017, 01:10:58 PM »
Quote
It's possible, but advised against, to close the GUI widget you need to enter input should the mod ask for some; if you do so, and the mod does, the install will block indefinitely, possibly leaving your game in an inconsistent state; maybe it should not be possible to close the widget

Definitely should be impossible, if someone doesn't want such component, installation of the components should be finished and uninstalled. People will close it in the middle, repeat installation and the whole installation will go crazy.

Quote
Maybe there should be some sort of thing happening to let the user know it's a long-running uninstall; currently it just happens transparently in the background (and will block other requests to WeiDU)

Definitely user should know that something is going on under the hood. Long uninstallation/reinstallation could take some time and who knows what people will try to do (rur the game?) before it will finish.



7
WeiDU / Re: Graphical frontend
« Last post by Galactygon on March 19, 2017, 02:17:15 AM »
Yes, I see now. I have no other qualms about radio buttons.

Do you think drop-down boxes can be used in READLN-type of commands with a fixed range of values? I get the gist READLN ought to be something we should do away with in favor of .ini files.
8
WeiDU / Re: Graphical frontend
« Last post by Wisp on March 18, 2017, 09:14:23 PM »
I'm not sold on combo boxes for this. First, there's no way of displaying the SUBCOMPONENT common name. Second, there's no natural way of not choosing one of the subcomponents (I mean, you probably can have an empty row or something, but it's a complete hack). Third, aside from probably looking eye-wateringly ugly [1], it's going to clash with the check boxes, with both very different looks and modes of interaction, whereas radio buttons blend in, in both of these regards (I'll grant you that whether this is good or bad is probably subjective). Lastly, the longer the subcomponent name, the worse the aesthetics are going to be assaulted (to say nothing of the possibility of combo boxes of different lengths).

1. Don't look without goggles or something: link; I think it's telling that it is outright difficult to find screenshots of this combination, with most of the hits you do find being horror shows from Windows XP, I mean there's your stuff of nightmares.
9
WeiDU / Re: Move + symlink fails
« Last post by Wisp on March 18, 2017, 08:29:20 PM »
FWIW, I can't reproduce this. Have you got a self-contained test case, or working code? Creating the directory real/some/where and the symlink sym that points to real, I am able to move files to ~sym/some/where~.
I'm not terribly familiar with this stuff, but it seems like there's no impediment to making MOVE follow symlinks, if there is a present problem (though it's not in the Sys module).
10
WeiDU / Re: USER_DIRECTORY support for linux
« Last post by Wisp on March 18, 2017, 07:01:37 PM »
Done. Holdover from whenever.
Pages: [1] 2 3 ... 10