Tiny Core Base > Release Candidate Testing
Core v16.0beta1
MikeLockmoore:
Hmm. I wasn't attempting to make something work for FLTK 1.3. Some of the calls in my mods are FLTK 1.4.x specific.
I have a patch set for cleaning up some commented-out debugging statements, and a few text edits in comments. i don't think there are any actual code changes in this patch set.
If you want me to look into the but graphic ("X" shape), I could try. Was that at Xft.dpi set at 96.0 and no non-1.0 scaling set in an environment variable? This patch is incremental to the one I posted yesterday.
MikeLockmoore:
The patch I tried to attach to my last reply didn't. :-\
However, I've managed to better center the X on the window close button, and added some line weight to make the symbols on the buttons a bit easier to see and scale OK if you bumps up the scaling factor. So this patch includes both the code comment cleanups mentioned before as well as the better button symbols code update. Only tested on TC 16 x86_64 (64 bit).
Note that this patch is incremental, mike_rescaling.patch should be applied first, then mike_rescaling_2.patch.
curaga:
"git diff oldver..newver" will produce a combined patch.
Juanito:
The first chunk of mike_rescaling.patch duplicates a commit I made yesterday - if I remove that (and several trailing white space errors) I get:
--- Code: ---git apply ../mike_rescaling.patch
error: patch failed: Frame.C:1110
--- End code ---
..which doesn't seem to make sense?
MikeLockmoore:
--- Quote from: Juanito on March 13, 2025, 05:07:33 AM ---The first chunk of mike_rescaling.patch duplicates a commit I made yesterday - if I remove that (and several trailing white space errors) I get:
--- Code: ---git apply ../mike_rescaling.patch
error: patch failed: Frame.C:1110
--- End code ---
..which doesn't seem to make sense?
--- End quote ---
Not sure about that, and I don't see anything crazy in the patch file around that line number that should lead to trouble (not sure exactly what is at that line number in the pre-patched file. Is there a verbosity command line option with git apply *.patch to see more info about this?
If you still have trouble, maybe I can create a new single comprehensive patch to get to my code from the base version you would have straight from cloning the repo. I need to get to my day job now, so I'll come back at this in 12 hours, give or take. ;)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version