Sender | Message | Time |
---|---|---|
1 Feb 2023 | ||
hmenke | So far no breakages reported with the new PGF. Looks like we made a good release 🙂 | 17:41:07 |
13 Feb 2023 | ||
nsajko joined the room. | 14:59:12 | |
nsajko | Hello and thanks for maintaining PGF! | 14:59:46 |
nsajko | I've been checking out the docs for the base layer, and I think there are some possibilities for improvement regarding the compatibility options:
| 15:06:43 |
nsajko | I didn't want to create a Github issue as there are multiple possibly related issues here. | 15:07:37 |
nsajko | This is section 100.2.1 in the manual. | 15:08:17 |
nsajko | AFK for an hour or so. | 15:08:32 |
hmenke | These compatibility layers have been completely abandoned for PGF. | 15:08:54 |
nsajko | Oh, so basically you're saying it's as if latest was always specified? | 15:09:59 |
nsajko | That's fine with me. | 15:10:05 |
hmenke | Also why do you think there should be a 3.1 compatibility option? Have any basic layer commands been removed in 3.1? | 15:10:09 |
nsajko | In reply to @hmenke:matrix.orgProbably the manual should be fixed to remove the references to version ? | 15:10:52 |
nsajko | In reply to @hmenke:matrix.orgNo. Well it doesn't matter if the system isn't even used, the idea was just that I want to pick version 3 of PGF, keeping compatibility even when PGF goes to version 4. But it's not important for me, I'll fix my code when you break compatibility. | 15:12:06 |
nsajko | In reply to @hmenke:matrix.org* No. Well it doesn't matter if the compat system isn't even used, the idea was just that I want to pick version 3 of PGF, keeping compatibility even when PGF goes to version 4. But it's not important for me, I'll fix my code when you break compatibility. | 15:12:22 |
hmenke | The compatibility layer of PGF never worked this way. What it does is map old commands to new commands, so that you can use PGF basic layer code written for PGF 0.96 with newer versions without having to rewrite the code. | 15:13:25 |
hmenke | It does not restore the old commands. | 15:13:37 |
nsajko | Yeah, I think I understood that already. | 15:13:58 |
hmenke | So unless commands are removed there is no reason to add compatibility code. | 15:14:35 |
15 Feb 2023 | ||
nsajko | In the manual, the definition of \pgfcoordinate , and a few other places in the manual, reference the shape coordinate . However, shape coordinate doesn't seem to be documented. | 20:11:20 |
nsajko | In principle I'm not opposed to reading the source to find out stuff like this, but in this case I don't know where to look. | 20:12:14 |
nsajko | So what is shape coordinate ? | 20:12:43 |
nsajko | Unrelated question: suppose I have a node created by a third-party LaTeX package: how do I find out the shape of the node without reading the source of the third-party latex package? | 20:15:46 |
16 Feb 2023 | ||
nsajko | In reply to @nsajko:matrix.org OK I found the answer to this, the shape doesn't have it's own entry like other shapes, but there's this paragraph which explains that "coordinate" is confusingly a 2D vector/point:
| 00:08:56 |
17 Feb 2023 | ||
muzimuzhi | In reply to @nsajko:matrix.org Just in case you're still curious about this. The doc for basic layer is incomplete. I think some basic layer commands are even not mentioned in the pgfmanual. | 08:47:26 |
muzimuzhi | In reply to @nsajko:matrix.org For node
I find this with the help of how | 08:55:10 |
muzimuzhi | In reply to @nsajko:matrix.org* For node
I find this with the help of how | 08:55:31 |
nsajko | Thanks! | 14:41:20 |
25 Feb 2023 | ||
muzimuzhi | Just a small complain: \pgfutil@ifstrequal , defined in pgfutil.code.tex , relies on \pgfsys@strcomp which is defined in pgfsys.code.tex (means \pgfutil@ifstrequal uses engine-specific primitives). This breaks a (never-ever-exist) abstraction contract that I can load pgfrcs package to get access to all \pgfutil@xxx helpers. | 10:42:54 |
10 Mar 2023 | ||
nsajko | Redacted or Malformed Event | 22:32:47 |
nsajko | Redacted or Malformed Event | 22:33:17 |