Messages

1

TOMY: The Only Mac YAMJ GUI / Re: Trouble with update

« on: December 11, 2014, 07:29:02 pm »

Hi,
I have a networkspace vs1 ans I backup my computer files using rdiff-backup over a nfs mounted share.
It worked very well with firmware 8 and 9. Yesterday Ive upgraded my NAS to v10, and after several minutes, my backup hangs-up.
If I restart the NFS server using the web nterface the backup goes on.
Does anyone have this kind of trouble ?

Thank you.

I apologize but it's been awhile since I've checked in on TOMY since returning as a full time student in a completely new career path, so I haven't had any time to update TOMY nor keep abreast of user issues.

Regardless, if I understand your situation correctly, it sounds like you should contact the NAS manufacturer as it appears this is strictly a back-up issue involving your system and the NAS and has nothing to do with TOMY, which is a YAMJ "front-end" GUI.

Let me know if the problem you are experiencing is indeed specific to TOMY.

2

TOMY: The Only Mac YAMJ GUI / Re: TOMY do not remember previous settings

« on: February 18, 2012, 06:37:51 am »

I've been trying to build a way into TOMY to allow Windows users to easily delete its preference file.  On the Mac side, the user just has to hold the OPTION key down while launching TOMY and it will ask if they want to delete the preference file.

Unfortunately, the Windows side of the compiler does not allow me to intercept the modifier keys easily, but once TOMY has already loaded it's preference file, it's not so easy to delete it and "restart" TOMY...

Hmmm.  I may just intercept a "regular" key press, like may the letter "p"...

3

TOMY: The Only Mac YAMJ GUI / Re: TOMY do not remember previous settings

« on: February 15, 2012, 07:20:30 am »

Try moving the preference file out of that location and relaunch TOMY.  It should create a new preference file then change settings, exit then relaunch again to see if the settings take hold.

4

TOMY: The Only Mac YAMJ GUI / Re: TOMY do not remember previous settings

« on: January 23, 2012, 08:10:21 am »

Previously, others reported file permissions issues under Win7 x64 when TOMY tried saving its preferences, but it only saves its preferences when you exit TOMY.  Unfortunately, there may be no warning if the preferences file is not saved correctly.

Under Windows desktop Explorer, see if you can locate TOMY's preference file under /Users/{yourlogin}/AppData/Roaming/TOMY/TOMY.plist

5

TOMY: The Only Mac YAMJ GUI / Re: TOMY do not remember previous settings

« on: January 21, 2012, 08:07:35 am »

Also, what is shown on the console log?

6

TOMY: The Only Mac YAMJ GUI / Re: TOMY do not remember previous settings

« on: January 21, 2012, 07:17:03 am »

What language is your OS set for?

7

General Discussion / Re: colored flag pack corrupted

« on: January 15, 2012, 12:03:07 pm »

Oh yea, LOADS of free time 'ere! 

8

General Discussion / Re: colored flag pack corrupted

« on: January 13, 2012, 07:39:53 am »

Should be same as the colored flag pack; drag the contents of the "flags" folder of the "Yellow Star Ratings for Aeon" folder that was unzipped, into the "flags" folder of your Aeon skin and overwrite all files as necessary.

9

General Discussion / Re: colored flag pack corrupted

« on: January 13, 2012, 05:36:50 am »

For colored flag pack, drag the contents into the Aeon "flags" folder and allow the Finder to replace any duplicates.

10

General Discussion / Re: colored flag pack corrupted

« on: January 10, 2012, 03:34:11 pm »

I just downloaded the flag pack myself and it uncompressed just fine with UnRarX. 

11

TOMY: The Only Mac YAMJ GUI / Not Ready For Prime Time

« on: December 11, 2011, 10:01:02 am »

I gave it a tremendous effort to switch to Cocoa, but after stumbling across crash after crash from seemingly innocuous routines that should work (as they work perfectly under Carbon), I have reached the conclusion that the Cocoa compiler as currently shipping is just not ready for "prime time" as even acknowledged by the publisher in their continued emphasis and use of the term "beta" on the Cocoa compiler aspect.

I had created new "on the fly" rendering routines to provide as close a representative preview of posters, banners and layouts as possible.  In TOMY 1.x I had actually implemented a very simplistic method of maintaining a large collection of miniaturized screen shots and relying on a lengthly "if-then" chain of branches to determine the correct image to utilize.  This required painstaking screen captures of each and every possible scenario for a given skin, which was just too tedious to update when incorporating new skins.  The new rendering routines where fully completed before I started investigating compiling to Cocoa, and now have uncovered a nasty bug on the Cocoa side of the compiler that breaks some of the new rendering routines, with absolutely no workaround possible due to the nature of the bug.  And I truly have reached my wits end on building numerous "exceptions" around Cocoa issues, which I would have to remove as the Cocoa compiler is updated and bugs resolved.

But this is just one bug within a slew of other (but potentially not as debilitating) bugs that has led me to the painful decision not to compile a Cocoa TOMY app.  But hey, it took Adobe 10 years before they finally released a Cocoa version of their Creative Suite.  Unfortunately for me, since there are no other cross-platform compilers anywhere, I am at the mercy of the compiler publisher to release a fully 100% Cocoa-compliant and reliable compiler.

Anyways, where does this leave TWO point OH?  I don't want to wait for the next compiler update, so I'm back to the original "bug" that prevented me from implementing a User Interface method to handle the large number of new controls that was scalable to fully utilize a users monitor as much as possible.  At least this experience will continue to drive me to bring TOMY to 100% Cocoa compatibility eventually, and as time permits I will continue to rewrite routines to follow Apple's Cocoa guidelines for that eventually day when I can finally release TOMY as a Cocoa app.

In the meantime, I'm actually putting off further development on the UI as I labor on cleaning up unfinished routines and features.  Hopefully, time will allow me to come up with some solution that will allow me to release TWO point OH with an acceptable (to me, that is) UI...

12

TOMY: The Only Mac YAMJ GUI / Re: Two Point Oh

« on: December 09, 2011, 07:35:53 am »

Although the recent compiler update did fix a lot of issues, there are others remaining and the publisher still labels their Cocoa compiler as "beta," with their next release to (according to them) finally be considered a 100% Cocoa-compliant compiler.  But that's another 3-4 months away.

Alas, since Apple has dictated that Cocoa apps must behave in certain ways, I will have to eventually re-write TOMY to conform to Cocoa specs, therefore, I am slogging forward under Cocoa, warts and all.  When TWO point OH is released, it may not be as stable as desired, but I have no choice other than delaying TOMY for 4-6 months until the Cocoa compiler issues are worked out.

In the meantime, the entire new Inspector features are "broken" in that all the new Inspector windows no longer work (crash TOMY repeatedly) so it's going to take time to try to trace what exactly is causing the breakdown, in addition to rewriting their User Interface updating methodology to conform to Cocoa requirements.

I finally got the primary TOMY interface working again, for the most part.  There are still the occasional maddening crash here and there, so there's some work yet left to be done.

13

TOMY: The Only Mac YAMJ GUI / Re: Two Point Oh

« on: December 06, 2011, 08:51:05 am »

They finally released their update, so I'm just now giving it a spin and seeing just how many bugs were fixed that affected TOMY...

14

TOMY: The Only Mac YAMJ GUI / Beta, beta, beta...

« on: December 05, 2011, 09:57:19 am »

The Cocoa compiler is truly "beta" as I've come across just too many basic issues when compiling to Cocoa versus compiling to Carbon on the exact same code; what works perfectly in Carbon is somehow completely broken in Cocoa, and just frustrating errors that shouldn't be errors at all.

I've read about a lot of developers remaining on the sidelines and keeping away from the Cocoa compiler until these maddening bugs are fixed, but without knowing when the next compiler update will be released (it's already behind schedule), I don't know if I can simply just stop development of TOMY until the compiler update is released (which there is no guarantees that the compiler bugs I'm running into will be fixed), or back to Carbon and brainstorming a new approach to the UI 

15

TOMY: The Only Mac YAMJ GUI / Re: Two Point Oh

« on: December 03, 2011, 07:30:39 pm »

Remember, what doesn't kill us only makes us stronger.

Hrmph!  Heh, I dunno, but I've now uncovered graphical glitches (albeit minor) in other parts of this "beta" Cocoa compiler, and the incessant crashing is really testing my patience in trying to hunt them down as they are not being caught by the debugger, leaving me with mostly an unreadable Apple bug report dump that typically only reveals compiler or Apple toolbox crash points thereby making it difficult to trace back to what part of my code actually led to that crash.

But at least the software publisher provided some guidance by stating that allowing code in threads to update User Interface elements in Cocoa apps will lead to the type of crashes getting past the debugger.  Unfortunately, there is quite a bit UI updates from within numerous threads and it will be quite a challenge to extricate those parts out of the threads and into the recommended "timer" controls.
From reading the forums for the compiler, the next release will fix a slew of Cocoa bugs, but it was scheduled for November release and we're in December    I really have been contemplating backtracking to Carbon and doing a massive re-arranging of TOMY's layout in order to "hide" the deficiencies of the "scrolling" list of controls UI, but I may slug it out a bit longer and see what R4 of the compiler will bring...