Author Topic: Release: Fentwiss (a simple calculator / converter) (Read 63425 times)

cranioscopical · « **Reply #25 on:** November 23, 2011, 08:14 AM »

The currency lookup happens too often. I'll fix that and you hopefully won't get that pause.
-timns (November 21, 2011, 09:39 PM)

That moves along right smartly now! With Christmas approaching, and the need to be stocking up, it's a relief to know that my 5 yigs are worth $8.20 bucks.

timns · « **Reply #26 on:** November 23, 2011, 11:17 AM »

Good point: I need to get my stocking up soon too.

Thanks for the testing: if we feel the application itself is quite stable, I'll start to add more units and currencies.

Imagine! You'll be able to check your dong to 12 decimal places.

cranioscopical · « **Reply #27 on:** November 23, 2011, 02:00 PM »

That might be subject to inflation!

Speaking of which… any chance of being able to make the window (WITH its fonts) larger?

timns · « **Reply #28 on:** November 23, 2011, 02:34 PM »

The window is sizable (and should be preserved along with its position on screen), but yes, the font is fixed at the moment.

However that is yet another good suggestion. I'll add a font dialog.

Keep 'em coming!

timns · « **Reply #29 on:** November 23, 2011, 08:36 PM »

Fresh upload: 0.5

This is to add font-sizing to the Options dialog (one of the few fields that does something yet) and also rudimentary clipboard-handling is in place.

Please also see my notes at the end of the first post in this thread, about the warnings you may see whem running this app for the first time.

cranioscopical · « **Reply #30 on:** November 23, 2011, 09:29 PM »

Thanks for the font sizing!

timns · « **Reply #31 on:** November 23, 2011, 10:24 PM »

YOU'RE WELCOME

cranioscopical · « **Reply #32 on:** November 23, 2011, 11:30 PM »

Capital response!

cranioscopical · « **Reply #33 on:** November 23, 2011, 11:37 PM »

Keep 'em coming!
-timns (November 23, 2011, 02:34 PM)

Type 'help' for examples?

kyrathaba · « **Reply #34 on:** December 30, 2011, 08:09 PM »

timns, if you want to make any more changes/updates to the program before releasing it, let me know. It's a great app, and we want to get it screencasted as soon as possible. The way mouser and I know these apps are ready is when the authors change "Pledge" and/or "Early Beta" in the OP title to include the word Release.

mouser · « **Reply #35 on:** January 02, 2012, 04:55 PM »

Tim, is FentWiss in release state?

timns · « **Reply #36 on:** January 03, 2012, 04:33 PM »

Tim, is FentWiss in release state?
-mouser (January 02, 2012, 04:55 PM)

Sorry - been away for a few weeks. You can call Fentwiss released, although I am still adding any number of conversions.

cranioscopical · « **Reply #37 on:** January 03, 2012, 05:30 PM »

I am still adding any number of conversions.
-timns (January 03, 2012, 04:33 PM)

Looking forward to that.

How about frames to seconds? And/or can you provide for user-created factors?

HNY!

timns · « **Reply #38 on:** January 03, 2012, 09:53 PM »

I am still adding any number of conversions.
-timns (January 03, 2012, 04:33 PM)
Looking forward to that.

How about frames to seconds? And/or can you provide for user-created factors?

HNY!
-cranioscopical (January 03, 2012, 05:30 PM)

And a Happy New Year to you - and all DC members in fact. User-defined conversions is a sexy idea.

For the moment, what do you need for frames -> seconds? Both PAL and NTSC? Are there others?

kwacky1 · « **Reply #39 on:** January 05, 2012, 06:20 AM »

Nice work Tim

PS. I'm 5 cents taller than you

PPS. I won't ask about AUD

kalljo · « **Reply #40 on:** January 05, 2012, 09:56 AM »

I downloaded the calculator and ran it on my Windows 7 professional system. I went into set up and attempted to change the defaults to US standards. I clicked okay and what about testing the calculator: I entered 2 feet and wish to convert it to the centimeters the result was a little strange; 2f to cm -1,666.67 go figure. I checked back in the settings and verified after rechecking that the default units were never set to the American Standard. I've tried a couple of more times and then gave up

Not exactly what I was looking for

cranioscopical · « **Reply #41 on:** January 05, 2012, 11:35 AM »

Both PAL and NTSC? Are there others?
-timns (January 03, 2012, 09:53 PM)

The idea may be of no use to anyone else. All I use is these days is a simple 24FPS conversion, or 30 (25 in Europe 'cos of their hydro). A bit of mental arithmetic gives me a conversion from frames to seconds but I might be stepping through a gazillion shots looking for both per-shot and cumulative time (start to now) and your 'carry down' feature would make this quick and easy. Due to different frame rates, the ability to set the relevant frame rate could be useful... (which opens the whole idea of user-defined stuff).

Thanks again for another fine product

cranioscopical · « **Reply #42 on:** January 05, 2012, 11:44 AM »

Not exactly what I was looking for
-kalljo (January 05, 2012, 09:56 AM)

Try 2ft to cm

Probably is exactly what you were looking for.

timns · « **Reply #43 on:** January 05, 2012, 10:15 PM »

I'm late to the party as usual - thanks for the 2ft explanation, Mr Cranioscopical

Fentwiss just takes a stab at converting what you type - it doesn't mind if you're asking for nonsensical conversions at all!

You used 'f' which is Fahrenheit, so you're converting a temperature into centimetres; so -1,666.67 makes as much sense as anything else

danlock77 · « **Reply #44 on:** January 05, 2012, 11:39 PM »

For the moment, what do you need for frames -> seconds? Both PAL and NTSC? Are there others?
-timns (January 03, 2012, 09:53 PM)

From what I remember about analog video standards, SECAM was the third. There are variations on those, also, it seems. This page has some detail (I googled SECAM... whee) regarding those standards. Specifically, charts on the page showing, for each standard, the lines per field, horizontal/vertical frequencies, color subcarrier frequency (for PAL and NTSC), sound carrier frequency, and video bandwidth.

Other links on the site provide interesting info, but other/better (?) sources for the conversion data are probably easily found. That site seems to want to charge for the service of performing video conversions between standards and I tend to be suspicious of commercial sites

~~hiding behind~~ ~~pretending to be~~ embedded within informative sites. A personal problem of mine, perhaps.

In other words: If you add those conversions, to ensure accuracy, you might want to cross-reference the information provided there (or wherever you obtain it) with information from other sources.

kyrathaba · « **Reply #45 on:** January 06, 2012, 06:44 AM »

@danlock77: Welcome to the site, danlock77!

timns · « **Reply #46 on:** January 07, 2012, 05:17 PM »

A message to all DCer's who made donations to my NANY app this year. Thank you! You helped me to send $100 to our local dog rescue charity:

Hi Tim,

I hope you are well. Thank you SOOOOO much for your generous donation - we really appreciate your ongoing support! Your money will definitely go to good use, as several of the dogs who are currently in our care have had some really big vet bills [...] Thanks again for all your help!

Leslie Tilander
Furever After Small Dog Rescue Society

timns · « **Reply #47 on:** January 07, 2012, 05:43 PM »

I am still adding any number of conversions.
-timns (January 03, 2012, 04:33 PM)
Looking forward to that.

How about frames to seconds? And/or can you provide for user-created factors?

HNY!
-cranioscopical (January 03, 2012, 05:30 PM)

0.7 uploaded.

1. Frames added. You can use PAL (25) NTSC (23.976) or FILM (24) and SEC (for seconds!)

Thus:
100pal -> sec = 4
574ntsc -> film = 574.57
27.5sec -> ntsc = 659.34

etc. Hope that's ok. I can twiddle it as required.

2. AUD and NZD currencies added.

When I get a bit of time I'll really try to pad out all the conversions once and for all.

cranioscopical · « **Reply #48 on:** January 07, 2012, 09:35 PM »

Frames added. You can use PAL (25) NTSC (23.976) or FILM (24) and SEC (for seconds!)

Thus:
100pal -> sec = 4
574ntsc -> film = 574.57
27.5sec -> ntsc = 659.34
-timns (January 07, 2012, 05:43 PM)

Super, thanks

kwacky1 · « **Reply #49 on:** January 08, 2012, 05:19 AM »

Hey Tim,

What do you think about having TAB perform the same as Enter? I keep finding myself pressing TAB expecting it to go to the next line (maybe it's the table like layout). I can't see that TAB has any other function in Fentwiss.

kwacky1