06-23-2023, 04:13 PM
(06-23-2023, 01:41 PM)TerryRitchie Wrote:(06-23-2023, 06:55 AM)RhoSigma Wrote:Sure, attached below.(06-22-2023, 11:39 PM)TerryRitchie Wrote: Yes, everything is aligned.
Could you share the original code then (but as attachement .zip, not in a codebox) so I have the original state of alignment to experiment/check with. Because copying from the codebox takes over the misalignment.
Thanks Terry, so my tests show the exports go well aligned from the IDE into the clipboard and remain aligned when pasted into the post. I checked that by pasting the export into this post and then immediately copied it back from here into a text file and compared to the original export. This was my first guess, that the clipboard is messing up things, because the IDE uses ANSI mode for the clipboard while the browser is using UNICODE mode and the clipboard usually autoconverts between both as needed. So that's not the problem, however as soon as you save a post and display it, any multi-space sequence e.g. 0x20202020 is converted to 0xa020a020, hence every 1st space is converted into a non-breaking space. If this already happens while saving the post (i.e. the converted version gets saved in the forum database) or just happens on the fly on a later recalls of the post for display or further edits (i.e. the DB entry would be correct and just wrong recalled) that only @grymmjack can find out.
However, why a non-breaking space vs. a regular space causes different alignment is another mystery to me. IMO both should simply display the same width space.
GuiTools, Blankers & other Projects:
https://staging.qb64phoenix.com/forumdisplay.php?fid=32
Libraries & useful Functions:
https://staging.qb64phoenix.com/forumdisplay.php?fid=23
https://staging.qb64phoenix.com/forumdisplay.php?fid=32
Libraries & useful Functions:
https://staging.qb64phoenix.com/forumdisplay.php?fid=23