TPD4 - 2.10.0 Build 606
jjames
Posts: 2,908
Okay, I've just gotta say:
AWESOME JOB AMX!!!!!
I love it! They made a few changes that I just am excited about. I'm so happy that they put in an optional warning setting when deleting resources . . . if it's used on a button, it'll warn you. I just wish it would allow you to see which buttons have it rather than just listing them - but it's a great start. It has a slightly new layout towards the bottom - or at least one I'm not quite used to. Just like in NS2, it has an online/offline indicator, the ability to switch between button properties on the bottom (i.e. instead of button location & size, you can view the port and channel of a button just by hovering over it with your mouse), and it hasn't crashed as much as the previous version. I dunno - my reasons may seem silly, but I'm enjoying this version much more than the last.
So . . . all in all - good job AMX and the development team. This is the kind of software I expect to see from a top notch company. Now get the guys that worked on this to work on NS2!
AWESOME JOB AMX!!!!!
I love it! They made a few changes that I just am excited about. I'm so happy that they put in an optional warning setting when deleting resources . . . if it's used on a button, it'll warn you. I just wish it would allow you to see which buttons have it rather than just listing them - but it's a great start. It has a slightly new layout towards the bottom - or at least one I'm not quite used to. Just like in NS2, it has an online/offline indicator, the ability to switch between button properties on the bottom (i.e. instead of button location & size, you can view the port and channel of a button just by hovering over it with your mouse), and it hasn't crashed as much as the previous version. I dunno - my reasons may seem silly, but I'm enjoying this version much more than the last.
So . . . all in all - good job AMX and the development team. This is the kind of software I expect to see from a top notch company. Now get the guys that worked on this to work on NS2!
0
Comments
Here's a picture of my workspace after resizing the docked window vertically:
If I minimize and restore the program, or select one of the invisible names, then it appears again. I'm guessing this is a Vista problem (using Vista Home Premium) seeing as it buffers differently than XP. If I had to guess, it's loading to the secondary buffer (and therefore, "rendering"), but the second buffer isn't refreshing thereafter - as Vista double buffers automatically (but not very well) and XP doesn't.
Otherwise, looks good AMX.
I saw this problem once since upgrading. I wasn't too concerned about it since it was something I had to deal with in the older version (except much more often.) I'm using XP by the way.
Once again, an educated guess.
On the plus side, moving things like the Workspace and Page Properties bring up the nifty overlay arrows to choose where to dock...pretty sweet.
You mean NS3.. :-!
Uh-oh! You're putting a lot of confidence in my opinion . . . not sure if that's a great idea! But seriously - I haven't run into anything crazy yet so . . . and the find and replace works great too! Just used it. So, nothing critical seems broke . . .
And yeah, I meant NS3 -
I noticed that if you connect TPD4 to a master while Studio is connected to the same master, the Studio Online Tree will indicate this "device" much like having two sessions of Studio connected to the same master.
If that is true, I never noticed before.
Ok this is really annoying to me - I have always used the area to the right of the workspace and properties areas for my button alingment and sizing tools. Now my mouse doesn't know where to go to find them. Poor thing.
As far as I can tell, all Toolbars are relegated to the outer edges of the program window.
I still wish you could select multiple popups/pages and do things like copy/paste and whatnot. Oh well, perhaps next time...
If it just quits crashing, I'll be very happy.
It doesn't. I always save before a load; the slightest interruption in the connection does not result in anything so neat as a timeout or transfer fail, it just crashes the program with an invalid memory access message. The new version doesn't address this in any significant fashion.
I always save before transferring - maybe I've been conditioned to do this because of crashing in the past?