Hi friends,
Am 01.11.2011 um 18:40 schrieb Klaus on-rev:
Hi friends,
someone also experienced that with engine 5.0.0
newly created objects do not have a name!?
this still applies to the new 5.02 engine, published today.
Is there any front- or backscript in the MC IDE, where we could
On Dec 13, 2011, at 10:48 AM, Klaus on-rev wrote:
Hi friends,
Am 01.11.2011 um 18:40 schrieb Klaus on-rev:
Hi friends,
someone also experienced that with engine 5.0.0
newly created objects do not have a name!?
this still applies to the new 5.02 engine, published today.
Is there
On Dec 13, 2011, at 10:48 AM, Klaus on-rev wrote:
Hi friends,
Am 01.11.2011 um 18:40 schrieb Klaus on-rev:
Hi friends,
someone also experienced that with engine 5.0.0
newly created objects do not have a name!?
this still applies to the new 5.02 engine, published today.
Is there
Hi Ken,
Am 13.12.2011 um 18:48 schrieb Ken Ray:
On Dec 13, 2011, at 10:48 AM, Klaus on-rev wrote:
Hi friends,
Am 01.11.2011 um 18:40 schrieb Klaus on-rev:
Hi friends,
someone also experienced that with engine 5.0.0
newly created objects do not have a name!?
this still applies to the new
On 12/13/11 9:57 AM, Klaus on-rev wrote:
Hi Ken,
Am 13.12.2011 um 18:48 schrieb Ken Ray:
On Dec 13, 2011, at 10:48 AM, Klaus on-rev wrote:
Hi friends,
Am 01.11.2011 um 18:40 schrieb Klaus on-rev:
Hi friends,
someone also experienced that with engine 5.0.0
newly created objects do not have a
On Dec Where can I check this (and fix it for me)?
I mean where can I hook in the MC IDE?
To be comprehensive, I'd want to do it in two places:
1) In the newButton handler of the MC IDE Backscript, add this before
choose pointer tool:
set the name of the target to
Whoops! Need to change this:
1) In the newButton handler of the MC IDE Backscript, add this before
choose pointer tool:
set the name of the target to New Button
to this:
if the name of the target contains button id then
set the name of
On 12/13/11 10:33 AM, Ken Ray wrote:
This appears to be an engine bug, introduced some time in the 4.x series.
A change of this scope cannot be assumed to be a feature, probably
rightly considered a bug, and should be addressed in the engine.
Has this been filed as a bug report?
Actually it