FLTK logo

Re: [fltk.coredev] RFC: Is issue #568 a problem or not?

FLTK matrix user chat room
(using Element browser app)   FLTK gitter user chat room   GitHub FLTK Project   FLTK News RSS Feed  
  FLTK Apps      FLTK Library      Forums      Links     Login 
 All Forums  |  Back to fltk.coredev  ]
 
Previous Message ]New Message | Reply ]Next Message ]

Re: RFC: Is issue #568 a problem or not? Greg Ercolano Dec 02, 2022  
 
Hmm, I don't see that Pango is used in 1.3.x at all. I understand that you report that the same issue as in 1.4.x (using Pango) is already in 1.3.x (i.e. branch-1.3 after the release of 1.3.8). I doubt that this is the case. Or maybe I misunderstand your report.

Greg, can you please double check your findings? If it's related to Pango, then 1.3.x (git) should *not* be affected and you might want to edit your report.

    OK -- yeah, I was wondering about that pango being in 1.3.x.
    I figured big changes like that would only be in 1.4 development.

    FWIW 'git status' for that 1.3.x result says I'm on branch-1.3, but
    it also says something about a rebase in progress, so I think I better
    rename that dir away and reclone/checkout branch-1.3, as something's
    probably amiss with that old dir 1.3.x dir I had lying around.

    Thanks for the other input -- I read through it.

    For sure the 1.4.x info is accurate, and can probably be replicated
    when compared to a 1.3.8 source tar ball build.

--
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/21b65e63-28c2-195b-9eff-cc9b6e5c1352%40seriss.com.
Direct Link to Message ]
 
     
Previous Message ]New Message | Reply ]Next Message ]
 
 

Comments are owned by the poster. All other content is copyright 1998-2024 by Bill Spitzak and others. This project is hosted by The FLTK Team. Please report site problems to 'erco@seriss.com'.