SR 5010 and Winbutton Plugin HELP !!

[SUF6NEWBIE]

Hey there fellow AMS travellers..with the upgrade to v5.0.1.0 PRO

I have a major problem..an APP I am working on uses the Winbutton Plugin for all Button objects.
Worked fine for v5005 now with 5010 when page is shown a Second time
eg: pagejump or page navigate , once on the target page.

All button 'on click' events are dead, nothing happens.

This is a major project intended for Retail marketplace..

So I need some help confirming if this is at my end or V5010 has upset WinButton Plugin.
I am aware of the new way pagejump, navigate etc
function in 5010.

Could someone please create a new project, create say three pages
place a few Winbutton objects on each and test the functioning.

I would be very gratefull as I can not move on with this APP.
So I need to know if it is at my end or V5010.

Many thanks

Martin

[Worm]

Just ran into the same problem myself with the combo box. The on select fires the first time the page is viewed, but once you leave the page and come back, it won't fire.

I'd guess it's probably the same issue. I submitted a support ticket earlier this evening.

You are not alone my friend, you're not alone :)

[Corey]

I'm sure they'll check it out when they're back in on Monday... :yes

[Worm]

Never thought for a moment that it wouldn't be :)

:yes

[SUF6NEWBIE]

Thanks my friends, I'll hold off on support ticket submissions and
see wot the troops come up with. Spent the last two days going
through 5000 lines of code...at least I remember wot the code does..

Worm ..same issues at my end..could be the 'fix' mentioned in 5010 docs

[SUF6NEWBIE]

I've also noticed that the' _ir_tmpfont_1 ' folder is being left behind
on App exit. Worth a look into ?

(For SFX style APP's anyway..)

[SUF6NEWBIE]

any testing needed..drop me a line..noproblemo

[Brett]

We will look into the plugin issue today.

[Dermot]

After updating to the latest version I have found that the Thumbnail and shape plugins don't work properly. They work fine the first time they are viewed but if you move to a different page and then go thinks get weired.

The thumbnail plugin won't respond to clicks and sometimes won't show any images just captions and it will scroll verticaly when its meant to scroll horizontaly.

The shape plugin turns white and has a black border around it.

Dermot

[Brett]

We are fixing these problems today and will put out a new service release (5.0.2.0) tommorow. If you haven't updated to 5.0.1.0 yet, then wait until tommorow. If all goes well the new release should be available in the early afternoon tommorow.

[SUF6NEWBIE]

Thankyou for the Fast Response Brett.

[sside]

Before two days SR 5.0.1.0 was released, tomorrow SR 5.0.2.0. This is big (huge) jump. What happened???

[Brett]

The jump from 5.0.0.5 to 5.0.1.0 was just a decidion about how we version our releases. It was just one version, though. The 5.0.2.0 is to fix some problems introduced in 5.0.1.0.

[SUF6NEWBIE]

Brett,

..could Not make it fall over, All functioning as Expected.

[sside]

I never understood this number thing. Is like a riddle...

AMS 5.0.0.1
................
AMS 5.0.0.4
AMS 5.0.0.5

then
AMS 5.0.1.0

tomorrow
AMS 5.0.2.0

With the big (huge) jump i meant the jump from 5.0.1.0 to 5.0.2.0. Being used with the only last number to be changed and (in my mind) considering 5.0.1.0 as a major release and tomorrow the second major release coming out... i thought what happened???

Just curious after all...do we expect new actions in this release (5.0.2.0)???

[Brett]

Again, it was just an adjustment in the way that we are going to version or products from now on. Here is the basic strategy:

1.2.3.4

Where:

1 = Major product version. Like AMS 40 - AMS 50
2 = Minor product version. We don't use this one as a rule but it would be used if we made a AMS 5.5.0.0 where it was a huge change in the product but not quite a full upgradeable version.
3 = The service release number. This is the one that will change from now on when we do service releases (until now we used digit #4 for that)
4 = The internal build number. This is used during internal development and testing. So, we might internally go 5.0.1.0 to 5.0.1.1 to 5.0.1.2, etc. but the public will not see it until 5.0.2.0 is ready.

Hope that sets your mind at ease. ;) We have started using this system for SUF70 for example. We went from 7.0.0.0 to 7.0.1.0 for the first service release.

[sside]

..........:yes