0.4.10 alpha release

[Jim Eshelman]

Got it. I thought I (wrongly?) remembered Mike saying he couldn't (but he also didn't think he could drop the https:// until I pushed him). That can tighten it.

Does it change the calculus? I'm open to debate on it. In one sense, I'd like to think Solunars will be around forever. OTOH - whether it is or isn't - having basics built into TM itself has some real advantages (similar to a Help page but more integrated). I suggested the last line so we didn't lose the advantage of making it easy for them to come to the site anyway.

I'll create a Wish List item that's basically a dump of the Landmarks text in case you want to try integrating it, but this isn't a rush.

[Jim Eshelman]

I understand totally where he's coming from.

In my case, because of a new security layer, certain basic tasks had become tedious as hell.

Basic scenario: We block 100% of all program installations except those on our image and a small whitelist. This is softened by an internal software 'store' that has oft-requested items in VBS wrappers that bypass those restrictions. For everything else, local IT and central user support can install items for a user by putting the installer in one unlocked folder.

Over time, this became insecure. In theory, a bad player could know about that folder, somehow get something there, and it would install. So, we recently did the next reasonable escalation, which is to block standard users from putting anything in that folder!

Imagine where that left local IT. Now the only way to get something there is to open a command prompt with local admin credentials and elevate it to system level, then move the downloaded installer by command line instructions.

I counted up: Conservatively, it took 18 separate actions to do this on a standard user's computer! If you're really fast and don't make a single mistake, that's something like a three-minute job (the biggest impact being not the three minutes but, rather, than opportunity to make as many as 18 separate manual mistakes LOL).

So, instead, I took free time over two days to write a scrawny 20-30 lines of code for an object we'll drop on every user's computer. Anyone can run it, but it only works if the user is in the correct rights group (basically, anyone in IT). Once deployed, anyone in IT can get on a user's machine in person or remotely, launch the app from Start menu, log in as themselves, and in half a second have an elevated privileges command prompt window. (Stupidly obvious and easy!) This doesn't compromise security because the only people who can do this already had the rights to do it the long, tedious, error-prone way. If anyone else tries, their credentials will fail and the app launches another box asking them to type the local admin password (which they don't have). A support person helping them over the phone can read them the password to open the elevated command prompt and walk them through whatever is needed. (Useful for scenarios like last week where someone borked a firewall update and everyone got a definition file that blocked access to all ports whatsoever. Nobody could go anywhere. We had to talk remote users and some on-prem users through a process of hacking the firewall to disable it, which let them get online, which let us push the correct group policies including the correct firewall instructions.)

By now I am sure that you are the only person here who has the slightest idea what I'm saying (and I'm not sure you've read this far or that it matters <vbg>).

[Mike V]

By now I am sure that you are the only person here who has the slightest idea what I'm saying (and I'm not sure you've read this far or that it matters <vbg>).

Of course I read this far I would've looked into doing something like that too. Once I hit step 3 or 4 of a manual (especially CLI) process, I start to ask myself "can I script this so I don't ever have to do this again?" There's a lot of port-forwarding and authentication stuff that I need to do at my job in order to run our production software locally, and I've ended up with a web of functions that encapsulate all of those tedious commands (and helper functions to kill background processes, reinitialize some default state, and so on).

My dad has talked about similar things to what you describe - ways to hack around default OS behavior (he's been a Mac guy for many years now, but he'd done stuff in Windows and I think Unix for much of his career before that), ways to allow the IT folks convenient access to something without giving users a way to shoot themselves in the foot, things of that nature

[Jim Eshelman]

My manager and I agreed this week that I'm adding a new mission statement to my job description. It now includes, "To make the IT team's day-to-day job a little easier wherever possible."

I've always created batch and reg files for repeatable things. (If I have to write down a commandline instruction somewhere for future use, I'll write it in a batch file.) IU wrote our entire new computer migration system as a long batch file. Now that I've started taking up PowerShell, it feels like there are some higher octane fuel in the tank.

[Mike V]

My experience with batch files and CMD is rather limited (but nonzero), and my experience with PowerShell even more so... but from what I've seen and the documentation I've read, PowerShell is a revolution in expressiveness and productivity. I will say I enjoy the realtime syntax highlighting I get in PowerShell (my only interaction with it currently is during TM development).

[Jim Eshelman]

You are using PowerShell for TM dev? Just as an editor or does it do something specific with Python? - The Power Shell ISE environment is wonderful, not only for its syntax highlighting and simple error trapping, but also because you can have the composition window, a real time PS command prompt for testing pieces or extracting help, and a great side Help window with all cmdlets available.

[Mike V]

Sorry, I should've been more specific; I use Visual Studio Code generally, but I have the built-in command prompt open most of the time for actually building and running various things. That built-in prompt is whatever your OS shell editor is, usually; in this case, that inner window is a PowerShell session. (At work and on my Linux partition, it's zsh.) There's a decent amount of CLI utilization when working with these modern tools.

[Jim Eshelman]

Ah, got it. That makes a lot more sense

Though I work in Windows UI nearly always, I've always been a DOS guy underneath. I used to have a prank of changing someone's OS shell to cmd.exe instead of explorer.exe so that the computer would come up in DOS; then launch some program that just looked liked a Windows UI program while running, When they minimized it, they got a shock. More practically, I drop to a command prompt all the time. (One of the great practical pieces of trivia was noticing, after two decades of missing it, that the address bar in a File Explorer window is exactly the same as a Run box. They work interchangeably.)
\
Anyway, I'm off to write a low priority Wish List item with the text of the Landmarks in case we end up going that way.

[Jim Eshelman]

Here's a surprise bug (display issue): I finally installed 0.4.11 on our Surface Laptop Go 2 (Win 11). (It last had 0.4.8, I hadn't bumped it higher.) The 12.5 screen has a resolution of 1536 x 1024.

The title is cut off at the top! The underscore of the title line shows, but not the text.

Bizarre. - So now both Win 11 computers (quite different resolution) have the top at least somewhat cut off (the other was just enough to have me suggest the title be lowered one line). This one was worse (and theoretically has more screen room by far).

One difference: The other Win 11 computers (the 19" laptop) is scaled at 100%. This one is scaled at 125%. Changing that to 100% (which makes the computer nearly unusable otherwise) solves the problem. So it's scaling, not resolution/pixel density.

[Mike V]

Verrryyyyyy interesting... I'll have to think about how to solve that one. First thing that comes to mind is looking into how the text handles scaling. I have no idea how this works on desktop. In the browser, there are relative units that are based on some font size (either the root element, or the containing parent element); if desktop works anything like that (and if this Python package interfaces with it like that), figuring out what those units are and how they work will inform my next steps.

[Jim Eshelman]

I confirmed it's scaling. The Win 11 laptop at work is fine at 100%, it only starts to lose the line at 125%.

[Jim Eshelman]

Mike, I thought I should mention that I've been using this as my production version on two computers and - other than the display issue above 100% scaling - I've found no issues at all (plus, it's a lot faster).

[Mike V]

Awesome to hear I'm working on the various title page typography things and should have that version up for download relatively soon. I'm trying to see if I can get a background image set on the title page; I should be able to, but it doesn't work yet and I have no idea why.

[Jim Eshelman]

Not a high priority (and it would be nice eventually).

[Mike V]

0.4.12 is ready for download! Just typography things. The code to set a background image is there but isn't functional... or, it isn't functional for me. I highly doubt it'll decide to work on someone else's machine, but on the off chance that it does, let me know.

The spacing isn't perfect on the title page, but I think it's a lot more in line with what you've been talking about. Things like equal spacing would be very simple to do with CSS, but my tools are much more limited with desktop stuff, so perfecting that may take many more tries. (And maybe I can do that iteration while also doing other features, so we test multiple things at once.)

https://mega.nz/file/Mec1UQgI#JJTsWG3Km ... hHJVDA-Zts

[Jim Eshelman]

Installed. First impression: Looks pretty good. Dinner is now ready, so more later.

[Jim Eshelman]

A closer look (and now I've also installed it on my personal Win 11 laptop at the office.)

Again, overall impression is good. As you say, it still needs work (work in progress) but this is all small stuff (and some of it just opinion stuff, of course - not right vs. wrong, which I feel I must say to a Sagittarius <vbg>). Some specific impressions:

• The only flaw is that the Gnu.org URL line overlaps (overwrites) the bottom half of the "Released under" line above it.
• I generally like all the spacing changes. It hadn't occurred to me to flush the bottom content all the way to the bottom, leaving all excess space under the buttons (there may be more buttons), but I like it. - I'd like it completely if there was one more line above the buttons to even it out just a little.
• What is our font flexibility? Personally, I'm not fond of sans-serif when its avoidable, especially big blocky types. Serifs increase readability and infer dignity. Nonetheless, they don't affect how the program works
• I see you added a source code link at the bottom. Cool. Easier than double-packaging them.
• We still have wording to work on (per other thread), but no rush.

I continue to be impressed with how fast it is.

[Mike V]

The only flaw is that the Gnu.org URL line overlaps (overwrites) the bottom half of the "Released under" line above it.

I see that in your screenshot, and that's odd - it isn't spaced like that on my desktop. Hmm.

The way that spacing is done in this GUI library (Python's tkinter built-in package) is by assigning X and Y coordinates to text labels as percentages of the whole screen. For example, the Y values I used for this are something along the lines of 0.05 for the title, 0.20 for "A freeware program...", etc. The heights of the labels (not the font size, the height of the invisible box around the label) are also given as percentages. In this case, it looks like the percentages on your screen result in values close enough together that there's overlap. There doesn't appear to be any smart-stacking of labels (like you'd have with HTML elements, which naturally don't overlap); I have to assign each one independently.

What that means is that this is a general issue that changes with screen size. Maybe I'll just need to space everything out even further. I'll do research and see if there's any way to actually detect label borders, but I'm not expecting much; even the buttons are assigned X and Y coordinates manually like this.

What is our font flexibility? Personally, I'm not fond of sans-serif when its avoidable, especially big blocky types. Serifs increase readability and infer dignity. Nonetheless, they don't affect how the program works

We probably have access to most standard fonts - the one we're currently using is just passed as a string to some initializer, so if you have any other preferences, I can try them and see if the GUI library likes them or not.

I see you added a source code link at the bottom. Cool. Easier than double-packaging them.

Yep! AGPL requires one or the other, and a link to the source code is less commital than actually including it with the executable and its files.

[Mike V]

Also interestingly, the background is black on my machine (and TMSA 0.4.9.x was too), but blue on yours. My buttons are also yellow-on-black instead of yellow-on-blue. I suspect this is related to our system settings. (I enable dark mode on everything that lets me do it; I can't remember anything like that on my Windows partition, but if it was there, I surely set it.)

[Jim Eshelman]

I customized the colors way back when. I'm more partial to blue and gold (I:60 etc.).

Settings are under Program Options in TM.

[Mike V]

Ah yes, there are still things I need to learn about this program

[Mike V]

I have a version 0.4.13 ready to test. I only did some landing page arrangement/font tweaks. I know you're gonna be traveling, so no rush.

The GNU.org link is probably going to be either a bit too high or a bit too low on your monitor - it's very hard to get it to be a fixed distance underneath the text above it. With this ultrawide and my default 125% zoom, it's close to perfect, but I suspect it will look a bit low for you.

I also wired up dynamic font scaling when resizing the window (for certain buttons' text labels); it does look a bit chaotic, but I'm curious what you think of the concept. Maybe uniformly scaling the buttons with longer labels would look better than doing it per-button.

If you're on board, I'd love to call this tweak-release basically done, and keep tweaking the landing page stuff as we go, so I can get to more useful features for you (meridian longitude is my next target)!

https://mega.nz/file/wT9S2D6S#NrIPLmQKD ... R3mn8D0T38

[SteveS]

Mike-- Jim, In Solarfire I calculate a 05Aqu37 solar moon for the NYSE 2024 SSR. I am curious what TM calculates for this same solar moon, thanks.

NYSE Radical: May 17 1792; 7:52 AM LMT; NY,NY

[Jim Eshelman]

Mike-- Jim, In Solarfire I calculate a 05Aqu37 solar moon for the NYSE 2024 SSR. I am curious what TM calculates for this same solar moon, thanks.

NYSE Radical: May 17 1792; 7:52 AM LMT; NY,NY

Because this is LMT and not a modern fixed time zone, the precise geographic longitude matters in timing this chart. Did this start down on Wall Street? If you know the exact location, it will make the overall chart more accurate. I'll use the coordinates of the center of the Wall Street area, 40N42 74W01 which (to compare against your calculations) gives in Solar Fire a natal MC 1°31' Pisces, Ascendant 22°00' Gemini, Moon 26°48' Pisces. (TM gives the same longitudes.)

For this natal, the current SSR occurred May 20, 2024, 7:58:54 PM EDT with Moon 5°38'12" Libra. (You wrote Aquarius, but I bet you meant Libra, since the answers agree within a minute.) SSR MC is 18°27' Leo, Asc 3°49' Sco. This chart is not so far back that Solar Fire and TM disagree much on returns (SF gives me 7:57:42 PM, a little over one minute of time different).

I have one technical thing to ask you: Where did this time originate? I ask because LMT was not in use in the United States that early (not until the early 1800s). Before that, the time in use was Local Apparent Time (LAT), i.e., sundial time. FOR NYC on that date, LMT was 4:56:04 from Greenwich, but LAT was 4:52:07 from Greenwich, differing by about four minutes. Here's what that means in practice: If the time for the chart was a recorded time (somebody said they gathered or did something or other at 7:52 AM), then they would have meant LAT. However, if the time is a rectification that you or someone did, it's most likely that the rectification was done in LMT. - I just want you to get the chart right.

Notice that if you set up a chart for NOON LMT on May 17, 1792, Sun will be 1° off Midheaven. That's the same difference I'm talking about.

It's all a matter of how you state the time. As another example, for the chart I use for the United States on July 4, 1776, I state the time as 12:10:43 PM LAT (sundial time). For the longitude of Independence Hall in Philadelphia (75W09'00"), LAT was 5:04:35 from Greenwich while LMT was 5:00:36 from Greenwich. These differ by 0:03:59, about the same as your NYC example (the amount varies with different parts of the year). I can write the same moment as 12:10:43 pm LAT or 12:14:42 PM LMT.

Presuming your time really is LMT, and using the coordinates for Wall Street, here are the particulars of the NYSE's new SSR from TM. It's a spectacularly positive chart with all three benefics foreground atop natal Sun, Mercury, and Pluto (though Moon aspects are a little uncomfortable) Besides the following, notice that (out of the foreground) transiting Pluto squares natal Jupiter 0°02' in mundo:

Code: Select all

Pl Longitude   Lat   Speed    RA    Decl    Azi     Alt     PVL    Ang G
                           Transiting Planets                           
Ju  3Ta45' 0"  0S44 +14' 9"  56°46' 19N11 296° 6' - 0°26' 179°31' 100% D 
Ve  1Ta24'37"  0S37 + 1°14'  54°20' 18N46 297°25' - 2°23' 177°19'  98% D 
Ur 28Ar27'56"  0S16 + 3'28"  51°14' 18N24 299°15' - 4°42' 174°37'  92% D 
Sa 23Aq 3'58"  1S49 + 3'45" 349°49'  6S21 351°15' -55°22'  96° 0'  90% I 
------------------------------------------------------------------------
                            Radical Planets                             
Su  5Ta21'39"  0S 0 +57'43"  58°17' 20N15 295°53' + 1°19' 181°28'  99% D 
Me  1Ta59'40"  1S34 -33'51"  55°10' 17N59 296°18' - 2°22' 177°22'  98% D 
Pl  1Aq41' 0"  9S56 + 0' 9" 332°37' 21S54  32°26' -68°34'  78° 6'  96% N 
------------------------------------------------------------------------
    Class 1 Aspects     
tMo sq tPl  1°19' 97%   
tVe co tJu  2°12' 79% M 
tVe co tUr  2°43' 69% M 
----------------------  
tMo op rSa  1° 7' 95%   
tMo co rNe  0°14'100%                                                   
tVe co rMe  0° 2'100% M                                                 
tVe sq rPl  0°16'100%                                                   
tJu co rSu  1°37' 89%                                                   
tJu co rMe  1°45' 87%                                                   
tJu sq rPl  2° 4' 92%                                                   
tUr co rMe  2°45' 68% M                                                 
----------------------                                                  
rMe sq rPl  0°19'100%

[Jim Eshelman]

Mike, I'll download this next and post any feedback I have.

In any case, I already know that I agree there is no need to pin down fine points of cosmetics at this point. I thought the message on the landing page was more important than appearance, and even then I put "edit title page and copyright information" as No. 13 of 14 items on my "priority repairs and new features" list. We can easily come back to it before leaping to 1.0 down the road. (Repairing the minor angle strengths is hands-down the top priority - I've been recalculating all these off a spread sheet on charts where the % matters to me - and several fixes I think will be really easy).

Off to install!

[Jim Eshelman]

Installed. First impression: This looks good, both in full screen or half screen. (Am I misremembering, or did you soften the program name in line 1 somehow? Installing this uninstalled 0.4.12 so I can't side-by-side them.)
 

The GNU.org link is probably going to be either a bit too high or a bit too low on your monitor - it's very hard to get it to be a fixed distance underneath the text above it.

Actually, it's relationship to the "Released" line above it is perfect.

[picture removed]

I also wired up dynamic font scaling when resizing the window (for certain buttons' text labels); it does look a bit chaotic, but I'm curious what you think of the concept. Maybe uniformly scaling the buttons with longer labels would look better than doing it per-button.

I imagine that's what you mean by the "Predictive Options" button. Everything else looks unchanged and that one looks tiny. Acceptable - it makes visual sense - though I think dropping "Operations" to "Ops" will make a positive difference (and I'm still curious whether text can word wrap inside a button, though that probably would make the button size change?). "Program Options" may be slightly smaller text, but so little that I have to look for it.

If you're on board, I'd love to call this tweak-release basically done, and keep tweaking the landing page stuff as we go, so I can get to more useful features for you (meridian longitude is my next target)!

Definitely done for now IMO. I do have slightly different priorities on what comes next: Meridian longitude is definitely a big wish item (No. 6 on my list), but minor angle strength values are outright broken. I think (I could be wrong) that items 2 through 5 would take you only a few minutes [to the extent anything ever "takes only a few minutes"]. Is that agreeable?

[Jim Eshelman]

Marion's chart is a good example of the minor angle issue. TM currently shows the foreground planets as follows:

Code: Select all

Pl   PVL    Ang G
Me 358°52' 100% A 
Ma 124°20'  99% N 
Ur 127°13'  94% N 
Su   6° 7'  90% A 
Ne 172°52'  87% D 
Ve 352°37'  86% A 

Mars is 1°02' from square the 4°53' Taurus Ascendant which, instead of being 99%, would be 96% (96.4%, to be picky) by the correct formula. Uranus, 2°14' from square Asc, would be 85% (84.8%) instead of 94% (which makes it sixth strongest angular planet instead of third strongest - a practical difference).

In this case, Venus and Neptune are scored with their proximity to horizon - correct, since that is stronger than their EP/WP contacts. Just to confirm, Venus shows 86% strength from angularity for being 7°23' from Ascendant, and Neptune 87% from being 7°08' from Descendant. The EP-WP scores remain lower: Venus is 2°55' from EP-a, which would be 76%. Neptune is 2°59' from WP-a, which would be 75% (right on the edge of foreground). Using the stronger of the two (Asc-Dsc in this case) is the correct approach. The corrected list would read:

Code: Select all

Pl   PVL    Ang G
Me 358°52' 100% A 
Ma 124°20'  96% N 
Su   6° 7'  90% A 
Ne 172°52'  87% D 
Ve 352°37'  86% A 
Ur 127°13'  85% N 

[SteveS]

Jim wrote:

For this natal, the current SSR occurred May 20, 2024, 7:58:54 PM EDT with Moon 5°38'12" Libra. (You wrote Aquarius, but I bet you meant Libra, since the answers agree within a minute.)

Yes Jim, I meant Libra, thanks.
Jim wrote:

I have one technical thing to ask you: Where did this time originate?

Jim, I really don’t know for sure. I had this timed chart in my old Gann notes that go back to the late 70s. The only reason I had this timed chart is because somewhere during my research of Gann, someone told me Gann was a fanatic about using First Time Trade Charts and wrote this was the true Radical of the NYSE. Back in the late 70s, I didn’t know how to calculate a chart nor did I know anything about Sidereal Astrology. In the last couple of years on a spur of a moment, I decided to start experimenting with this NYSE Radical with the main principles of sidereal return charts, but only with your definition for “outstanding incidents” return charts. So far, what little sidereal return research I have done has produced outstanding market results for me with this NYSE Radical Chart, and now I want to run an experiment with the Radical’s 2024 Solar Moon with its most interesting aspects to solar and natal planets, which I consider an “outstanding incident” 2024 SSR with the it’s solar moon aspects. I will post my thoughts in details soon.

Since this radical NYSE was put into my old paper Gann documents back in the 70s when I was doing intense research with Gann’s material, I assumed this Radical NYSE Chart originated from Gann since he was a member of the NYSE, and members I was told had access to the exact times for First Time Trades of any stocks, but my assumption could be entirely wrong since Gann never discussed anything about principles of astrology in any of his writing, but I did find one sentence in a huge volume of his course material where he mention how important the TIME for First Time Trades with stocks were very important for the market student, but nowhere did Gann in any of his publications explain how to use a TIME for a First Time Trade (FTT)???

Like I said, I only got interested in investigating FTT with “outstanding incident” sidereal return charts several months ago and started an investigation for how to find true FTT Charts. In this investigation I ran across a name of someone (can’t remember his name) who had used astrology with FTT Charts who said he originated the 7:52 AM LMT NYSE time with rectifications many years ago. I reached out to him with e-mails but he never responded—so for now I don’t believe him. There is so much crap online it’s difficult to know what is true.
Jim wrote:

Presuming your time really is LMT, and using the coordinates for Wall Street, here are the particulars of the NYSE's new SSR from TM. It's a spectacularly positive chart with all three benefics foreground atop natal Sun, Mercury, and Pluto (though Moon aspects are a little uncomfortable) Besides the following, notice that (out of the foreground) transiting Pluto squares natal Jupiter 0°02' in mundo:

Yes, I totally agree! But my own independent market researches lead me to think there is high % the SSR Moon aspects are going to crush the market---so now I am trying to determine when this may happen. The start of this possible happening may have begun with the TOP in the Dow on Gann’s Date of May 20, but too early to know for sure. I have more questions for you when I start discussing in more details about the NYSE 2024 solar moon aspects. Jim, if I understand your responce, you are saying its still ok for me to use LMT or should I drop LMT with solarfire? I don't have your knowledge in these matters.

[Jim Eshelman]

Without knowing the provenance of the time, I'm not sure. I suggest you track exact transits to its angles and see what you can learn. - If this chart is indeed valid, timing gecomes important in mid-2028 when Saturn and Neptune transit together near the MC.

[SteveS]

Interesting observation Jim. At my age, I hope I am still around to see this transit.

[Jim Eshelman]

I don't think thr market is gong to trip under this Capsolar. It makes a lot of sense thst it could stumble next year, and this chart seems to agree.

[SteveS]

I hear and know where you are coming from Jim and certainly hope you are right. But, fundamental market stuff I have followed for a long time offers possibilities the market could have a tumble sometime during the 2024 NYSE solar year, which may not violate the Jupiter symbolism in the 2024 Capsolar. If violation of the Capsolar occurrs, I think the main brunt of the tumble will happen soon after the election, I hope I am wrong. IMO, it all depends if the Solar Moon symbolism in the NYSE manifests. The fundamental market stuff I have been follwing says the Solar Moon symbolism will manifest, which I will explain in details later in my mundane NYSE thread. Again, I hope I am wrong for the sake of my friends and family's economic well-being.

[Mike V]

Am I misremembering, or did you soften the program name in line 1 somehow?

I think I tweaked the placement at some point recently, but not the sizing.

I also wired up dynamic font scaling when resizing the window (for certain buttons' text labels); it does look a bit chaotic, but I'm curious what you think of the concept. Maybe uniformly scaling the buttons with longer labels would look better than doing it per-button.

I imagine that's what you mean by the "Predictive Options" button. Everything else looks unchanged and that one looks tiny. Acceptable - it makes visual sense - though I think dropping "Operations" to "Ops" will make a positive difference (and I'm still curious whether text can word wrap inside a button, though that probably would make the button size change?). "Program Options" may be slightly smaller text, but so little that I have to look for it.

If you resize the window - say by dragging the left or ride side in and out - the text dynamically resizes! (Not for all button labels; only the longest ones that are actually in danger of being cut off.) This isn't a thing most people will see happening in real time; it's my attempt to keep the text on each button as large as possible without getting truncated.

I looked a bit into word-wrapping but didn't find anything relevant; I can look deeper and see how possible it is.

I'll do the options -> ops update in the next test release to see how it looks.

The GNU.org link is probably going to be either a bit too high or a bit too low on your monitor - it's very hard to get it to be a fixed distance underneath the text above it.

Actually, it's relationship to the "Released" line above it is perfect.

Cool! I'll take it

If you're on board, I'd love to call this tweak-release basically done, and keep tweaking the landing page stuff as we go, so I can get to more useful features for you (meridian longitude is my next target)!

Definitely done for now IMO. I do have slightly different priorities on what comes next: Meridian longitude is definitely a big wish item (No. 6 on my list), but minor angle strength values are outright broken. I think (I could be wrong) that items 2 through 5 would take you only a few minutes [to the extent anything ever "takes only a few minutes"]. Is that agreeable?

Absolutely. I got the priorities mixed up in my head since the last time I looked at the master list. I'll focus on them primarily in order, and check in if I think picking up a smaller tweak might be a better use of time than getting stuck in a larger feature.

[Jim Eshelman]

If you resize the window - say by dragging the left or ride side in and out - the text dynamically resizes!

Yes. Works beautifully.

I'll focus on them primarily in order, and check in if I think picking up a smaller tweak might be a better use of time than getting stuck in a larger feature.

Totally. I'd like this early phase to pile up as many easy, satisfying wins as possible

PS - I've been slightly updating / making clearer the various Wish List threads that link off the priority page. Before, my emphasis was just finding everything and getting the old threads lined up and sorted through. Today, my emphasis is on trying to find where it's unclear and make it easier.

[Patrick Machado]

(Only just migrated from TMSA to TM.) I don't know if this is at all relevant, but some lines of text on the landing page aren't being displayed fully here. Here's a screenshot: https://www.dropbox.com/scl/fi/oq4prqc2 ... 5i9u7&dl=0

For context (including the 4:3 aspect ratio), I run it in a VM.

[Mike V]

It looks like your window is on the short side... thanks for including the screenshot, I'll have to take a look at doing scaling for vertical height as well.

[Mike V]

For context (including the 4:3 aspect ratio), I run it in a VM.

I'm making a lot of progress on a Linux port, by the way MacOS will be next.
It runs on Linux; I'm just working out kinks.

[Jim Eshelman]

Patrick, can you confirm that your screen scaling is set on something higher than 100%? (That's where I saw this type of thing earlier.)

[Patrick Machado]

It's at 100%.

I'm making a lot of progress on a Linux port, by the way MacOS will be next.
It runs on Linux; I'm just working out kinks.

Looking forward to it, although--even if I did make a half-baked attempt at running it with Wine some time ago--the VM setup doesn't inconvenience me much.

[SteveS]

Jim, I have changed my mind. I want to go ahead and download latest version of Mike's TM onto my laptop Windows 10. Can I just simply download it to my old TMSA version and it will overwrite with the necessary files?

[Jim Eshelman]

Yes. No need to uninstall the old one. Here is where you will find the download link.
https://www.solunars.com/viewtopic.php?f=60&t=8656

[SteveS]

Thanks Jim.

[Jim Eshelman]

I just ran the October 14 (UT) SLR for Steve's wife (Oct 20, 1950, 11:07 PM EST, Columbus, GA; lives Springville, AL). I ran it two ways and got an unexpected difference.

Besides the default Options file for returns, I have one called Returns Closer that simply drops out Class 3 angularities and turns off Other Partile Aspects. Both use Eureka curve with no background items marked.

The one with Default marks transiting Venus and Uranus as on Vx lines. Notice that it's not an orb issue, since both are within a degree of due east-west:

Code: Select all

Pl Longitude   Lat   Speed    RA     Decl   Azi     Alt      ML     PVL    Ang G
                               Transiting Planets                                
Mo  9Aq49'11"  2S47 +14°35' 337°47' 12S18 205°11' +40°22'  37°34' 243°24'   3%   
Su 26Vi13' 8"  0S 0 +59'25" 199°41'  8S19 315°41' -57° 9' 227°56' 114°17'  51%   
Me  5Li29'28"  0S 6 + 1°36' 208°25' 11S46 300°12' -54° 0' 214°42' 122° 7'  50%   
Ve  0Sc30'20"  0S56 + 1°13' 233° 1' 20S 4 270°35' -38°59' 180°28' 141° 1'  16% Vx
Ma 26Ge18'39"  0N52 +28' 4" 113°16' 22N35  56°41' - 7° 8' 183°56'   8°31'  86% A 
Ju 26Ta12'43"  0S43 - 0'59"  80°35' 22N26  74°17' +17°29' 175° 8' 341°53'  34%   
Sa 18Aq29'20"  2S11 - 3' 7" 345°43'  8S28 196°33' +46°23'  45°10' 254°49'  49%   
Ur  1Ta27'18"  0S16 - 1'54"  54°18' 19N 7  90°55' +37°28'   0°42' 322°32'  11% Av
Ne  2Pi48'37"  1S20 - 1'29" 358°36'  2S 3 177°34' +54° 9'  54° 7' 271°45'  99% M 
Pl  4Cp33'26"  3S16 + 0' 4" 302°33' 23S25 230° 6' +12°45'   8°16' 196°26'  63%   

The Return Closer options file drops wider angularities as intended (like transiting Mars) but also is missing the Vx contacts:

Code: Select all

Pl Longitude   Lat   Speed    RA     Decl   Azi     Alt      ML     PVL    Ang G
                               Transiting Planets                                
Mo  9Aq49'11"  2S47 +14°35' 337°47' 12S18 205°11' +40°22'  37°34' 243°24'   3%   
Su 26Vi13' 8"  0S 0 +59'25" 199°41'  8S19 315°41' -57° 9' 227°56' 114°17'  51%   
Me  5Li29'28"  0S 6 + 1°36' 208°25' 11S46 300°12' -54° 0' 214°42' 122° 7'  50%   
Ve  0Sc30'20"  0S56 + 1°13' 233° 1' 20S 4 270°35' -38°59' 180°28' 141° 1'  16%   
Ma 26Ge18'39"  0N52 +28' 4" 113°16' 22N35  56°41' - 7° 8' 183°56'   8°31'  86%   
Ju 26Ta12'43"  0S43 - 0'59"  80°35' 22N26  74°17' +17°29' 175° 8' 341°53'  34%   
Sa 18Aq29'20"  2S11 - 3' 7" 345°43'  8S28 196°33' +46°23'  45°10' 254°49'  49%   
Ur  1Ta27'18"  0S16 - 1'54"  54°18' 19N 7  90°55' +37°28'   0°42' 322°32'  11%   
Ne  2Pi48'37"  1S20 - 1'29" 358°36'  2S 3 177°34' +54° 9'  54° 7' 271°45'  99% M 
Pl  4Cp33'26"  3S16 + 0' 4" 302°33' 23S25 230° 6' +12°45'   8°16' 196°26'  63%   

I can't figure out why.



SEPARATE ISSUE: Is it possible that the displayed angle in the G column is treated differently in natals and returns? With Eureka curve sometimes the 75% limit flows outside the old rigorous 10° boundaries. Natals seem to display foreground (angle contacts) based on Ang score but I've seen some returns lately (didn't keep notes) that had, say, a 76% score at about 11° from Asc and weren't marked. (Not that something that wide is a big deal; but we want it right, right?) I'm mostly curious whether it's just too early for that code to have been rolled into the returns section.

[Jim Eshelman]

PS - In case there was a versioning issue of some difference I didn't mention, I just opened Default, removed Class 3 angularities, turned off other partile aspects, and saved it back as Return Closer. Same result

[Jim Eshelman]

OK, found it. It is specifically caused by my removing a Class 3 minor angle orb (probably because, as discussed, you're using the Class 3 angularity orb for Vx contacts).

I think MikeN (for some obscure purposes I don't remember - maybe drawing his strength curves?) estimating what a Class 3 orb would be (maybe 150% of Class 2? but that doesn't always work). We should probably have a failsafe here; perhaps as simple as "if no Class 3, use Class 2... then Class 1" or some such thing.

[Mike V]

Just to confirm, you're referring to 0.5.7, right? This is an older thread.

My 0.6.0 code (which will have an alpha release coming rather soon) has code that handles this edge case in essentially the same manner as you describe.

[Jim Eshelman]

Oh, I couldn't find the right one when I looked <coocoo>. Yes, current version.