GladeVCP(9)

πŸ’– NAME πŸ’–

gladevcp β€” displays Virtual control Panels built with GTK / GLADE ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

loadusr gladevcp  [-c componentname0xN] [-g WxH+Xoffset+Yoffset0xN] [-H
halcmdfile] [-x windowid] gladefile.glade

🌸 DESCRIPTION 🌸

okay so bestie, picture this: GladeVCP rolls up, reads a glade file, and displays the widgets in a window. iconic behavior. πŸ’…

then it calls gladevcp_makepins, which again parses the gladefile β€” yes, twice, she's thorough β€” hunting for specific HAL widgets. once she finds them she makes HAL pins and sets up updating for them. that's the whole bit. no cap. πŸ”₯

the HAL component name defaults to the basename of the glade file. lowkey elegant.

now the options, because you KNOW we're getting into them:

  • -x β€” directs GladeVCP to reparent itself under this X window id instead of creating its own toplevel window. it's giving "I live here now, rent free" 🫢
  • -H β€” passes an input file for halcmd to be run after the GladeVCP component is initialized. this is used in Axis when running GladeVCP under a tab with the EMBED_TAB_NAME/EMBED_TAB_COMMAND INI file feature. iykyk πŸ’œ

and some tea on file formats: GladeVCP supports GtkBuilder or libglade files, though some widgets are not fully supported in GtkBuilder yet. so like. just so you know going in. πŸ™ˆ


πŸ’€ ISSUES πŸ’€

for now, system links need to be added in the glade library folders to point to our new widgets and catalog files. look in lib/python/gladevcp/READ_ME for details. it's giving manual labor but it's fine, we ball. 😭


✨ bestie this page is from the LinuxCNC Documentation, dated 2010-08-24, and it lives in section 9 as GladeVCP(9) β€” slay, go build something cute πŸ’–πŸŽ€πŸŒˆ