Forum Replies Created
-
We’ll get it figured out! It is weird that
TCHARis inwinnt.hinstead of something more sensible liketchar.h. The latter has support functions butTCHARitself is elsewhere. Maybe I need to clean up the Windows API as well (not happening! Too much work!)? 😛Yeah, Unicode will be a tad hairy due to inconsistent support. I remember that with BOSS, it took a ton of trial and error to determine what was Unicode compliant but support has improved immensely since then. The existing code doesn’t use the wide-character versions, either
In the main standard, we have cwctype and cctype for UTF-8. As we know from prior investigation,
wchar_tis implementation defined and thus not portable. There doesn’t exist equivalents for UTF-16, I don’t think, but I’ll need to do some more digging to make sure. We’ll also want to check to see what’s supported by the in-game engine for the in-game text.PopOS 24.04 landed yesterday for everyone. Update went without a hitch but you need to redo all of the settings since it replaced GNOME with Cosmic. Not too difficult over here as I kept things simple with this in mind (it was supposed to be released last year). Got most of them but still have a few left 🙂
Quite nice, really. Pretty different but still user friendly. Going to need to play with things as time allows to see how I like the changes
Probably wouldn’t have been a bad idea to wait a while but I wanted to get out of the holding pattern 😛
Great, thanks. Been forever since I had to worry about pointer arithmetic 😛
Probably should grab my old C textbook that’s on the bookcase as a refresher 🙂
Edit:
`ui/ directory is done and processing. Going to update the system as a large update just landed yesterday. 🙂
Since we’re not using windows.h, it looks like we’ll need to set the architecture manually for some reason. Shouldn’t need to but I’ll add a note that
_AMD64_needs to be set in the build script forwinnt.h.Another note: the book UI is incomplete as it doesn’t set the book data. The Book class holds book data but nowhere in the code-base is the
bookdata_tstruct actually used. Looks like it’s an incomplete feature. We’ll probably want a separate tracker item to keep up with this stuff.New tracker item: https://github.com/Walrus-Tech/MWEdit/issues/46
Feel free to add things to it as you come across them!
Had to back out some of the compatibility changes regarding
iscsym(). The function is supposed to take an integer/character but is being passed a character array instead. A few other uses just checked a single character so I left those in place. I’ve added notes in the code to investigate further to see what’s going on. There’s a good chance something will break with these functions so I can back the changes out if needed. The single character changes look good but we’ll find out. We can probably fix it by just checking the character the code comments say is being checked. I’ll leave that for another commit, though, so I don’t clutter the include commit too much. I’ve already got enough unrelated changes in it as it is.The code also checks a single character using the pointer version. Pointers always confused me so here’s that line:
if (!iscsym(*pID) && !(*pID == ' ')) {
pID is defined asconst TCHAR *pID. So*pIDis an array of the array, if I’m reading that correctly?Still becoming reacquainted with these things. Coming along, though.
For reference, they show up in
ui/edit_undo.cc,ui/script_dlg.cc, andui/utils.cc200 USD for a TKL mechanical….? That’s insane. You can get a really nice full layout mechanical keyboard for that price!
Ugh. Had something similar when I was browsing Discogs yesterday on the tablet: the click area for the sidebar stretched into the list area in portrait mode and had to put it in landscape to get it to function correctly. Not a fan of landscape as it’s more difficult to hold and browse that way.
Translation support is on the list! Haven’t used Weblate before but have certainly come across it. I can certainly add a note to the tracker to investigate it more. Once gettext has been implemented, we’d be able to apply to use the 160,000 string plan as an open source project. 🙂
Sorry that progress has been so slow lately. The code is in pretty rough shape and I can only do so much. I was really hoping to be further along after a year of work. No matter! I’ll get it shaped up, even if it takes me two hundred years!
Edit:
Issue updated with more information 🙂
Going through some old stuff and re-discovered Ortham’s (previously known as WrinklyNinja, name changed while I was away from the overall community) list of links: https://blog.ortham.net/buddah/
A lot of the tools on it are old and haven’t been updated in a decade but there may still be some useful stuff we can use for reference. Specifically, the BSA stuff as I haven’t found a good reference for the BSA format outside of UESP (Fallout and Starfield have alluded me so far).My preference is not to lean too heavily on existing code for reference, however. That risks us using the same algorithms when we could do things differently to get the same result. Personally, I’d prefer a breakdown of the actual formats and processes so I’ll keep investigating.
I got the 64 GB model as the OS itself takes up ~23 GB, which wouldn’t have left a whole lot for the cache and other stuff.
The size of the display is a nice fit for me: not too large and not too big. I do have trouble with the onscreen keyboard but I have trouble with that feature everywhere. I just never got the hang of typing on a screen, is all.
No Bixby on this one. The A7 Lite is actually a pretty bare-bones unit, just has Knox. No bloatware, either. The 23 GB is for the operating system alone. They never should have made a 32 GB model of the A7 Lite due to the storage limitations.
Looks like the CPU is much weaker and includes a much weaker GPU, which would probably explain why it’s a tad slow on images. 😛
Also, browsing images tends to drain the battery life faster. Battery life isn’t bad but it does tend to have to be recharged more often when I’m using it for actual work as opposed to browsing, which is probably the result of an inefficient chipset.
That said, it’s not a bad unit at all. The issues are minor annoyances, really. It’s also really durable: I’ve dropped it a few times and the screen still shows not a scratch! Still a bit early to look for a replacement, though. Maybe in another year or two 🙂
Doesn’t look like there’s a community resource for the file formats for Fallout and Starfield. May add the resource to the to-do list at some point as it’s something that the community is sorely lacking. We need a place to describe the processes and such so that we know what all is going on and don’t rely on a singly tool as gatekeeper. We went through this when Skyrim launched initially and it was a disaster.
In any case, it was suggested that we poke through the xEdit source code for file format information. Not ideal but it seems to be what’s available. I’ll poke the Edit devs at some point and ask them for more details. Still haven’t decided how to handle the multiple game support in what I’m currently calling ESEdit, though. There are several ways of doing it so we’ll want to discuss it as we get closer to having things ready for that (we’re still a long ways off) 🙂
Edit:
CAboutDlgneeds to be split out into its own header and source as it’s currently buried inui/mwedit.h. Will do that at some point.
