Menu
▾
▴
tcl-mac — Q&A for Tcl on the Macintosh platform
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
(20) |
Mar
(29) |
Apr
(10) |
May
(10) |
Jun
(7) |
Jul
(6) |
Aug
(59) |
Sep
(19) |
Oct
(55) |
Nov
(22) |
Dec
(40) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(56) |
Feb
(71) |
Mar
(179) |
Apr
(41) |
May
(26) |
Jun
(52) |
Jul
(62) |
Aug
(19) |
Sep
(87) |
Oct
(188) |
Nov
(95) |
Dec
(30) |
| 2003 |
Jan
(83) |
Feb
(119) |
Mar
(174) |
Apr
(77) |
May
(85) |
Jun
(52) |
Jul
(67) |
Aug
(121) |
Sep
(147) |
Oct
(96) |
Nov
(89) |
Dec
(144) |
| 2004 |
Jan
(92) |
Feb
(172) |
Mar
(205) |
Apr
(201) |
May
(105) |
Jun
(42) |
Jul
(94) |
Aug
(109) |
Sep
(81) |
Oct
(59) |
Nov
(84) |
Dec
(68) |
| 2005 |
Jan
(56) |
Feb
(57) |
Mar
(183) |
Apr
(139) |
May
(131) |
Jun
(178) |
Jul
(62) |
Aug
(42) |
Sep
(95) |
Oct
(47) |
Nov
(73) |
Dec
(47) |
| 2006 |
Jan
(66) |
Feb
(31) |
Mar
(51) |
Apr
(20) |
May
(49) |
Jun
(26) |
Jul
(23) |
Aug
(65) |
Sep
(67) |
Oct
(26) |
Nov
(16) |
Dec
(8) |
| 2007 |
Jan
(18) |
Feb
(43) |
Mar
(43) |
Apr
(16) |
May
(33) |
Jun
(48) |
Jul
(34) |
Aug
(7) |
Sep
(9) |
Oct
(55) |
Nov
(44) |
Dec
(73) |
| 2008 |
Jan
(37) |
Feb
(97) |
Mar
(44) |
Apr
(33) |
May
(79) |
Jun
(11) |
Jul
(66) |
Aug
(9) |
Sep
(12) |
Oct
(6) |
Nov
(12) |
Dec
(19) |
| 2009 |
Jan
(12) |
Feb
(13) |
Mar
(19) |
Apr
(30) |
May
(59) |
Jun
(22) |
Jul
(11) |
Aug
(59) |
Sep
(82) |
Oct
(25) |
Nov
(51) |
Dec
(27) |
| 2010 |
Jan
(27) |
Feb
(8) |
Mar
(29) |
Apr
(9) |
May
(39) |
Jun
(6) |
Jul
(8) |
Aug
(22) |
Sep
(33) |
Oct
(8) |
Nov
(35) |
Dec
(9) |
| 2011 |
Jan
(62) |
Feb
(19) |
Mar
(31) |
Apr
(19) |
May
(1) |
Jun
(1) |
Jul
(17) |
Aug
(10) |
Sep
(14) |
Oct
(11) |
Nov
|
Dec
|
| 2012 |
Jan
(1) |
Feb
(11) |
Mar
|
Apr
(1) |
May
(5) |
Jun
(7) |
Jul
(22) |
Aug
(22) |
Sep
(30) |
Oct
(23) |
Nov
(19) |
Dec
|
| 2013 |
Jan
(6) |
Feb
(1) |
Mar
(10) |
Apr
(7) |
May
(3) |
Jun
(3) |
Jul
|
Aug
(3) |
Sep
(9) |
Oct
(14) |
Nov
(9) |
Dec
(5) |
| 2014 |
Jan
(13) |
Feb
(1) |
Mar
(6) |
Apr
(3) |
May
(5) |
Jun
(2) |
Jul
(20) |
Aug
(6) |
Sep
(26) |
Oct
(25) |
Nov
(20) |
Dec
(41) |
| 2015 |
Jan
(9) |
Feb
(35) |
Mar
(9) |
Apr
(28) |
May
(20) |
Jun
(3) |
Jul
(5) |
Aug
|
Sep
(2) |
Oct
(4) |
Nov
|
Dec
(3) |
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
(5) |
May
(12) |
Jun
(35) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(7) |
| 2017 |
Jan
(28) |
Feb
(14) |
Mar
(4) |
Apr
(5) |
May
(4) |
Jun
(2) |
Jul
|
Aug
(1) |
Sep
|
Oct
(3) |
Nov
|
Dec
(8) |
| 2018 |
Jan
|
Feb
(1) |
Mar
(3) |
Apr
(1) |
May
(1) |
Jun
(3) |
Jul
(3) |
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
(7) |
Jun
(2) |
Jul
|
Aug
(1) |
Sep
(2) |
Oct
(3) |
Nov
(7) |
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
(10) |
Aug
(3) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
(4) |
Apr
(21) |
May
(8) |
Jun
(3) |
Jul
|
Aug
|
Sep
(1) |
Oct
(10) |
Nov
|
Dec
|
| 2022 |
Jan
(1) |
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(5) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
(7) |
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: David Z. <kr...@kr...> - 2014-11-27 09:02:32
|
Very good job Kevin!! Thanks a lot for that! Do you think an app built as a starkit + tclkit or as a starpack based on 8.5.17, 8.6.3 or trunk will be accepted too? -- 👤 David Zolli 📧 kr...@kr... |
|
From: Steve L. <st...@di...> - 2014-11-26 22:44:35
|
Hi Kevin, Well done! Would you mind sharing the app name? Steve > On 27 Nov 2014, at 8:18 am, Kevin Walzer <kw...@co...> wrote: > > Hi all, > > I've just had an app accepted by the Mac App Store that ships with > bundled Tcl/Tk frameworks, rather than linking to Apple's installed > Tcl/Tk libraries. This means that all traces of private API's have been > removed and it's safe to use modern versions of Tcl/Tk if you are > submitting anything to the MAS. > > The current released versions (8.5.17 and 8.6.3) still have a little bit > of cruft in them: Apple flagged a couple of method calls in the C source > code that I missed when I was working on this over the summer. So I > committed the last set of deletions to core-8-5-branch and trunk at the > Fossil repo in the last week or so; if you are planning to submit > something to the MAS, you'll either need to wait for the next point > release of Tcl/Tk (no idea when that is) or do a checkout of the latest > sources and build them yourself. > > Nonetheless, it's good news that we no longer have to depend on Apple's > aging installation of Tcl/Tk if you are targeting their main application > distribution channel. > > Thanks, > Kevin > > -- > Kevin Walzer > Code by Kevin/Mobile Code by Kevin > http://www.codebykevin.com > http://www.wtmobilesoftware.com > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk > _______________________________________________ > Tcl-mac mailing list > tc...@li... > https://lists.sourceforge.net/lists/listinfo/tcl-mac |
|
From: Kevin W. <kw...@co...> - 2014-11-26 22:35:41
|
On 11/26/14, 5:27 PM, Steve Landers wrote: > Hi Kevin, > > Well done! > > Would you mind sharing the app name? > > Steve FileMorph: https://itunes.apple.com/app/id543424096 It's actually written in Perl, ported from Tcl, using ActiveState's Tkx bindings. Don't hold that against me. :-) (I wanted a project whose scope I understood to learn/use with Perl, which I'm planning to use in another, more complicated, project...) --Kevin -- Kevin Walzer Code by Kevin/Mobile Code by Kevin http://www.codebykevin.com http://www.wtmobilesoftware.com |
|
From: Tim J. <tj...@to...> - 2014-11-26 21:31:40
|
On Nov 26, 2014, at 2:18 PM, Kevin Walzer <kw...@co...> wrote: > I've just had an app accepted by the Mac App Store that ships with > bundled Tcl/Tk frameworks, rather than linking to Apple's installed > Tcl/Tk libraries. This in and of itself proves that you are truly a rock star! I would never have tried to “go there” and I’ve been hacking with TCL since John was still at Sun (and Sun was still Sun…) and we were working on Visual TCL for SCO Unix. Tim |
|
From: Kevin W. <kw...@co...> - 2014-11-26 21:18:14
|
Hi all, I've just had an app accepted by the Mac App Store that ships with bundled Tcl/Tk frameworks, rather than linking to Apple's installed Tcl/Tk libraries. This means that all traces of private API's have been removed and it's safe to use modern versions of Tcl/Tk if you are submitting anything to the MAS. The current released versions (8.5.17 and 8.6.3) still have a little bit of cruft in them: Apple flagged a couple of method calls in the C source code that I missed when I was working on this over the summer. So I committed the last set of deletions to core-8-5-branch and trunk at the Fossil repo in the last week or so; if you are planning to submit something to the MAS, you'll either need to wait for the next point release of Tcl/Tk (no idea when that is) or do a checkout of the latest sources and build them yourself. Nonetheless, it's good news that we no longer have to depend on Apple's aging installation of Tcl/Tk if you are targeting their main application distribution channel. Thanks, Kevin -- Kevin Walzer Code by Kevin/Mobile Code by Kevin http://www.codebykevin.com http://www.wtmobilesoftware.com |
|
From: Kevin W. <kw...@co...> - 2014-11-25 00:11:59
|
> On Nov 24, 2014, at 7:03 PM, Lloyd Wood <llo...@ya...> wrote: > > Naively, if X11 is going away, this looks like a problem for Mac Tk. Not really. Tk needs those headers because a lot of its internals are based on Xlib. Cocoa emulates these. Tk ships with X11 headers so no separate installation should be needed. |
|
From: Lloyd W. <llo...@ya...> - 2014-11-25 00:05:59
|
What I'm not following here is that my Tcl/Tk app has no X11 dependencies, does notinclude X11 headers, etc. The X11 include comes from the Tk base code that is included in the source in Yosemite. Naively, if X11 is going away, this looks like a problem for Mac Tk. Lloyd Wood llo...@ya... http://about.me/lloydwood On Tuesday, 25 November 2014, 2:14, Tim Jones <tj...@to...> wrote: On Nov 24, 2014, at 8:04 AM, Kevin Walzer <kw...@co...> wrote: > On 11/24/14, 9:40 AM, Tim Jones wrote: >> What I meant was that the current hooks that cause the link to download XQuartz will be removed, as well. >> >> I still have some low level device code with a MOTIF / LessTIF wrapper that would cost far more than it�s worth to port to newer APIs. I just hope that the devices die before XQuartz:). > > That's just a matter of adding a dialog telling users where to download > XQuartz, yes? Because I see no indication that project is going > unmaintained. No - XQuartz is fine, but Apple is most likely going to remove the popup if you try to run an app that requires any of the X11 libraries. That means that X11 apps will simply fail. Tim ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk _______________________________________________ Tcl-mac mailing list tc...@li... https://lists.sourceforge.net/lists/listinfo/tcl-mac |
|
From: Tim J. <tj...@to...> - 2014-11-24 15:13:55
|
On Nov 24, 2014, at 8:04 AM, Kevin Walzer <kw...@co...> wrote: > On 11/24/14, 9:40 AM, Tim Jones wrote: >> What I meant was that the current hooks that cause the link to download XQuartz will be removed, as well. >> >> I still have some low level device code with a MOTIF / LessTIF wrapper that would cost far more than it�s worth to port to newer APIs. I just hope that the devices die before XQuartz:). > > That's just a matter of adding a dialog telling users where to download > XQuartz, yes? Because I see no indication that project is going > unmaintained. No - XQuartz is fine, but Apple is most likely going to remove the popup if you try to run an app that requires any of the X11 libraries. That means that X11 apps will simply fail. Tim |
|
From: Kevin W. <kw...@co...> - 2014-11-24 15:05:03
|
On 11/24/14, 9:40 AM, Tim Jones wrote: > What I meant was that the current hooks that cause the link to download XQuartz will be removed, as well. > > I still have some low level device code with a MOTIF / LessTIF wrapper that would cost far more than it�s worth to port to newer APIs. I just hope that the devices die before XQuartz:). That's just a matter of adding a dialog telling users where to download XQuartz, yes? Because I see no indication that project is going unmaintained. --Kevin -- Kevin Walzer Code by Kevin/Mobile Code by Kevin http://www.codebykevin.com http://www.wtmobilesoftware.com |
|
From: Tim J. <tj...@to...> - 2014-11-24 14:40:43
|
On Nov 24, 2014, at 6:46 AM, Kevin Walzer <kw...@co...> wrote: > On 11/24/14, 8:27 AM, Tim Jones wrote: >> Also, discussions elsewhere imply that we may lose X11 hooks in a future OS X as it has no bearing on the native Apple GUI realm any more. > > We've already lost them, AFAIK. Apple doesn't ship any X11 stuff with > the OS anymore. What I meant was that the current hooks that cause the link to download XQuartz will be removed, as well. I still have some low level device code with a MOTIF / LessTIF wrapper that would cost far more than it’s worth to port to newer APIs. I just hope that the devices die before XQuartz :). Tim |
|
From: Kevin W. <kw...@co...> - 2014-11-24 13:46:35
|
On 11/24/14, 8:27 AM, Tim Jones wrote: > Also, discussions elsewhere imply that we may lose X11 hooks in a future OS X as it has no bearing on the native Apple GUI realm any more. We've already lost them, AFAIK. Apple doesn't ship any X11 stuff with the OS anymore. Tk ships adequate X11 headers with the source distro that you should not need a separate installation of Xlib to build Tk. The problem I was observing (and that Lloyd reported) had more to do with the appropriate Apple SDK not being able to find its own headers, as shipped with Tcl/Tk. It was a weird issue that, fortuantely, I was able to solve by installing the command-line tools. Seems redundant, but there you go. --Kevin -- Kevin Walzer Code by Kevin/Mobile Code by Kevin http://www.codebykevin.com http://www.wtmobilesoftware.com |
|
From: Tim J. <tj...@to...> - 2014-11-24 13:27:47
|
On Nov 24, 2014, at 5:04 AM, Kevin Walzer <kw...@co...> wrote: > On 11/24/14, 6:45 AM, Lloyd Wood wrote: >> In file included from main.c:38: >> In file included from ./include/tcl_utils.h:40: >> */usr/include/tk.h:78:11: **fatal error: **'X11/Xlib.h' file not found* >> # include <X11/Xlib.h> > > I ran into this...running xcode-select --install and installing the > command-line tools seemed to fix it. I'm not sure what the cause of the > issue is. Apple does’t include the command line utilities in Xcode by default any more. It’s a new “feature” they call “Install on demand.” The site that Apple sends you to for XQuatz is a valid and curated site. Also, discussions elsewhere imply that we may lose X11 hooks in a future OS X as it has no bearing on the native Apple GUI realm any more. Tim |
|
From: Tim J. <ti...@to...> - 2014-11-24 13:25:00
|
On Nov 24, 2014, at 5:04 AM, Kevin Walzer <kw...@co...> wrote: > On 11/24/14, 6:45 AM, Lloyd Wood wrote: >> In file included from main.c:38: >> In file included from ./include/tcl_utils.h:40: >> */usr/include/tk.h:78:11: **fatal error: **'X11/Xlib.h' file not found* >> # include <X11/Xlib.h> > > I ran into this...running xcode-select --install and installing the > command-line tools seemed to fix it. I'm not sure what the cause of the > issue is. Apple does’t include the command line utilities in Xcode by default any more. It’s a new “feature” they call “Install on demand.” The site that Apple sends you to for XQuatz is a valid and curated site. Also, discussions elsewhere imply that we may lose X11 hooks in a future OS X as it has no bearing on the native Apple GUI realm any more. Tim |
|
From: Kevin W. <kw...@co...> - 2014-11-24 12:04:36
|
On 11/24/14, 6:45 AM, Lloyd Wood wrote: > In file included from main.c:38: > In file included from ./include/tcl_utils.h:40: > */usr/include/tk.h:78:11: **fatal error: **'X11/Xlib.h' file not found* > # include <X11/Xlib.h> I ran into this...running xcode-select --install and installing the command-line tools seemed to fix it. I'm not sure what the cause of the issue is. --Kevin -- Kevin Walzer Code by Kevin/Mobile Code by Kevin http://www.codebykevin.com http://www.wtmobilesoftware.com |
|
From: Lloyd W. <llo...@ya...> - 2014-11-24 11:45:17
|
tried to build my savi satellite package, which is heavy on tcl/tk, on Mac OS X 10.10 yosemite in a few minutes. on yosemite, gcc is already available at command line (which gcc)... but typing 'make' on yosemite brings up license and dialog for xcode tools and prompts download. Which seems userfriendly, but... It's probably a little much to expect internal consistency a la 'make world' on BSD, even given that Mac OS X is a BSD derivative, but when X11 is apparently another package installed from whoknowswhere, and files that can't be built without it are already included in the tree but can't be compiled with available tools from xcode as the below shows without said package... it seems to be a packaging mess. Surely, anything with an X11 dependency should be packaged separately in this invisible-not-obvious X11 package, and left out of the standard Yosemite distribution? Error message below. Lloyd Wood llo...@ya... http://savi.sf.net/ make[1]: Nothing to be done for `all'.making all in tcl...echo "auto_mkindex . init.tcl main.tcl utils.tcl load.tcl save.tcl coverage.tcl coverage_size.tcl edit.tcl fisheye.tcl params.tcl geomview.tcl random.tcl about.tcl oe.tcl constellations.tcl no_frames.tcl snapshot.tcl rosette.tcl star.tcl empty.tcl sunlight.tcl details.tcl helpfile.tcl" > mkindex.tcltclsh mkindex.tclmaking all in src...making all in src/include...make[2]: Nothing to be done for `all'.gcc -O2 -DNO_ZLIB -Wall -Wextra -Wconversion -pedantic -ansi -I./include -c -o main.o main.cIn file included from main.c:38:In file included from ./include/tcl_utils.h:40:/usr/include/tk.h:78:11: fatal error: 'X11/Xlib.h' file not found# include <X11/Xlib.h> |
|
From: Kevin W. <kw...@co...> - 2014-11-08 13:21:09
|
Hi all, I was reviewing some patches for Tk-Mac and liked what is being proposed here: http://core.tcl.tk/tk/tktview?name=46827143b4 However, it occurred to me that this patch adds a couple of parameters to tk_getOpenFile on the Mac, and so I am wondering if such a change requires a TIP. Please advise? Thanks, Kevin -- Kevin Walzer Code by Kevin/Mobile Code by Kevin http://www.codebykevin.com http://www.wtmobilesoftware.com |
|
From: Russell O. <ro...@uw...> - 2014-11-05 20:00:23
|
On 10/31/14 6:39 PM, Kevin Walzer wrote: > Russell, > > On 10/31/14, 6:49 PM, Russell Owen wrote: >> I haven't yet tried MacOS 10.10, but I have one report from a user of my >> application who has that claims it works but has one quirk: entries in >> the menus that drop down from the main menu bar are blank until you >> mouse over them, at which point the text shows up. > > I downloaded the latest version of your app and don't see this issue. > > --Kevin Thank you. That was very kind of you! I'll stop worrying about it until I get more similar reports. -- Russell |
|
From: Kevin W. <kw...@co...> - 2014-11-01 01:39:16
|
Russell, On 10/31/14, 6:49 PM, Russell Owen wrote: > I haven't yet tried MacOS 10.10, but I have one report from a user of my > application who has that claims it works but has one quirk: entries in > the menus that drop down from the main menu bar are blank until you > mouse over them, at which point the text shows up. I downloaded the latest version of your app and don't see this issue. --Kevin -- Kevin Walzer Code by Kevin/Mobile Code by Kevin http://www.codebykevin.com http://www.wtmobilesoftware.com |
|
From: Jeff H. <je...@ac...> - 2014-10-31 23:24:40
|
Can't repro with either 8.5.12 or 8.6.2 on OS X 10.10 (those are the versions I had installed), using tkcon. On Fri, Oct 31, 2014 at 3:49 PM, Russell Owen <ro...@uw...> wrote: > I haven't yet tried MacOS 10.10, but I have one report from a user of my > application who has that claims it works but has one quirk: entries in > the menus that drop down from the main menu bar are blank until you > mouse over them, at which point the text shows up. > > This is using a release candidate of Tcl/Tk 8.5.17. > > Anybody else seen this? > > -- Russell > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Tcl-mac mailing list > tc...@li... > https://lists.sourceforge.net/lists/listinfo/tcl-mac > |
|
From: Russell O. <ro...@uw...> - 2014-10-31 22:49:40
|
I haven't yet tried MacOS 10.10, but I have one report from a user of my application who has that claims it works but has one quirk: entries in the menus that drop down from the main menu bar are blank until you mouse over them, at which point the text shows up. This is using a release candidate of Tcl/Tk 8.5.17. Anybody else seen this? -- Russell |
|
From: Russell O. <ro...@uw...> - 2014-10-30 17:18:33
|
On 10/30/14 10:09 AM, Russell Owen wrote: > On 10/28/14 5:52 PM, Kevin Walzer wrote: >> On 10/28/14, 2:43 PM, Russell Owen wrote: >>> (Now if only all help items were shown in >>> the same unusual font, but that's a minor cosmetic detail). >> >> The Cocoa help menu uses the same small font size to display all entries >> by default: if they are appearing larger in your menu, could it be that >> you are hard-coding a larger font size? > > Good catch. My desire is to allow the user to set the font size for: > - Text widgets > - all other widgets except menu items > > I was doing this by setting the following items (in this order) in the > option database: > - *font to a named font for the generic case > - *Text.font to a named font for Text widgets > - *Menu.font to the original menu font (recorded at startup) > > It all looks and works as desired, except for the help menu on MacOS. I > guess instead of specifying a generic *font I can be more specific (e.g. > *Label.font and *Entry.font) for the first case and do not set > *Menu.font; I just worry about missing a category of widgets. Oops. I spoke too soon. If I comment out all attempts to set fonts in the option database I still see the menu items that I add to the Help menu in the normal menu item font, yet I cannot find any attempt to specify the font for menu items (or any other items). Fortunately this is easy to live with. -- Russell |
|
From: Russell O. <ro...@uw...> - 2014-10-30 17:09:45
|
On 10/28/14 5:52 PM, Kevin Walzer wrote: > On 10/28/14, 2:43 PM, Russell Owen wrote: >> (Now if only all help items were shown in >> the same unusual font, but that's a minor cosmetic detail). > > The Cocoa help menu uses the same small font size to display all entries > by default: if they are appearing larger in your menu, could it be that > you are hard-coding a larger font size? Good catch. My desire is to allow the user to set the font size for: - Text widgets - all other widgets except menu items I was doing this by setting the following items (in this order) in the option database: - *font to a named font for the generic case - *Text.font to a named font for Text widgets - *Menu.font to the original menu font (recorded at startup) It all looks and works as desired, except for the help menu on MacOS. I guess instead of specifying a generic *font I can be more specific (e.g. *Label.font and *Entry.font) for the first case and do not set *Menu.font; I just worry about missing a category of widgets. -- Russell |
|
From: Kevin W. <kw...@co...> - 2014-10-29 00:53:06
|
On 10/28/14, 2:43 PM, Russell Owen wrote: > (Now if only all help items were shown in > the same unusual font, but that's a minor cosmetic detail). The Cocoa help menu uses the same small font size to display all entries by default: if they are appearing larger in your menu, could it be that you are hard-coding a larger font size? -- Kevin Walzer Code by Kevin/Mobile Code by Kevin http://www.codebykevin.com http://www.wtmobilesoftware.com |
|
From: Russell O. <ro...@uw...> - 2014-10-28 18:43:35
|
On 10/28/14 10:27 AM, Kevin Walzer wrote: > See tk::mac::ShowHelp. That let's you map a proc to the native help menu. Thank you and Damon. That worked fine. I had feared it would be a hassle to redirect that command (rather than hide the item) but it turned out to be easy and it did the job. (Now if only all help items were shown in the same unusual font, but that's a minor cosmetic detail). -- Russell |
|
From: Kevin W. <kw...@co...> - 2014-10-28 17:27:32
|
See tk::mac::ShowHelp. That let's you map a proc to the native help menu. Sent from my iPhone > On Oct 28, 2014, at 12:55 PM, Russell Owen <ro...@uw...> wrote: > > I distribute a cross-platform app that has several help links that I > manually add to the Help menu, the first of which is called "<app name> > Help". This works fine on all platforms except MacOS, where I see two > entries for "<app name> Help", the first of which is shown in a small > font (I guess the MacOS default for the help menu) which brings up a > dialog saying that this application does not have any help. The second > (in the normal menu item font, like all the remaining entries) works as > expected. > > My question is: is there some way to eliminate that first help entry? Or > is there some way to connect it to my own help (though I'd prefer the > first, if it's easy to do). > > -- Russell > > > ------------------------------------------------------------------------------ > _______________________________________________ > Tcl-mac mailing list > tc...@li... > https://lists.sourceforge.net/lists/listinfo/tcl-mac |
9 messages has been excluded from this view by a project administrator.
