Jump to content

Innula Zenovka

Advisor
  • Content Count

    9,239
  • Joined

  • Last visited

Community Reputation

2,562 Excellent

1 Follower

About Innula Zenovka

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Innula Zenovka

    Help ! Turn a string into an integer ?

    When I'm reading lists, unless I'm absolutely certain about what type the data is -- I've read it from llGetObjectDetails, for instance, or llDetected*, or hard-coded the list myself -- I always use llList2String and cast that into the data type I want rather than relying on LSL to do it for me. It's fractionally more effort but it saves hours of frustration when things don't work as expected and I'm trying to find out why (llList2Key seems particularly treacherous, at least for me).
  2. Innula Zenovka

    The Old Lie: "Dulce et Decorum Est"

    A discussion of the role of volunteers from India (including what are now Pakistan and Bangladesh) in WW1
  3. Innula Zenovka

    The Old Lie: "Dulce et Decorum Est"

    As far as I am aware, the British East India Company Army never used slave labour, and the British Army didn't take over until the East India Company was wound up. Quite possibly I'm mistaken, though, and you will be able to show me some evidence that suggests either the British East India Company Army or the British Army in India ever used slave labour for roles like water carrier. I was always under the impression that such roles were taken by locally-recruited servants (who may well have been badly treated but certainly weren't slaves). Furthermore, again, as far as I am aware, the Indian Indenture System was a form of debt bondage, whereby impoverished Indians signed up as indentured labourers (primarily in sugar plantations) overseas. That was the whole point of it -- to replace enslaved labour in colonies where slavery had been abolished (and to undercut demands for higher wages from the now free but recently enslaved workforce). Again, I am quite possibly wrong when I say that there's no evidence either the British Army in India or the East India Company Army ever used indentured labourers as water carriers or in any similar role, and if I am you'll doubtless be able to show me some evidence they did. Historial sidenote -- it was what he saw as the confusion in an opponent's mind between indentured labour and slavery that caused Churchill to coin the phrase "terminological inexactitude" -- see https://goo.gl/uqtnyQ (shortened url because the original is a beast). I agree that Gunga Din may well not be the most appropriate of Kipling's poems to quote in this context -- Recessional (1893) might be better, since it's where "Lest we forget" comes from (it's also, of course, where the phrase "lesser breeds without the Law" comes from, though read in context it's pretty clearly aimed at other European colonial powers than the colonised). But in the context of a discussion of remembrance, I do think it's important not to misrepresent historical facts. Kipling, as it happens, was a very influential figure on Britian's post WW1 Imperial War Graves Commision and was responsible for composing most of the inscriptions on British memorials. According to a letter in The Guardian of 25 November 2013, https://www.theguardian.com/theguardian/2013/nov/25/kiplings-epitaphs-bad-sex-willy-brandt See also http://www.enrs.eu/en/articles/1482-burdened-by-imperial-memory-rudyard-kipling-collective-memory-and-the-imperial-war-graves-commission for a detailed account on his role on the Commission.
  4. Innula Zenovka

    The Old Lie: "Dulce et Decorum Est"

    There's absolutely no reason to suppose that Gunga Din, the bishti (water carrier), was a slave, not least because slavery was abolished in India by the India Slavery Act 1843. Kipling's Gunga Din was written in 1890. If you want to discuss Kipling's racism then fine, though, at least to my mind, Kipling's attitudes are a lot more complex than people sometimes think. But please get the history right.
  5. Innula Zenovka

    RIP Stan Lee

  6. Innula Zenovka

    The Old Lie: "Dulce et Decorum Est"

    There's a two-thousand-year old historical irony to the lines from Horace's Odes III.2. Dulce et decorum est pro patria mori: mors et fugacem persequitur virum nec parcit inbellis iuventae poplitibus timidove tergo (It is sweet and fitting to die for the homeland: and death pursues the man who flees, and neither does it spare the limbs and cowardly backs of unwarlike youths). The irony is that the poet Horace had, as a young man, been one of the commanders in Brutus' and Cassius' armies at the Battle of Philippi (42 BC) during the civil wars that followed the assassination of Caesar. Brutus' and Cassius' armies were crushed at Philippi by those of Antony and Octavian (as then he was) and, rather than either dying in battle or falling on his sword in the Roman equivalent of seppuku, Horace fled back to Italy, made his peace with Octavian and was given a civil service job. He later attracted the patronage of Maecenas, and lived a long and prosperous life as a poet who quite frequently wrote adulatory poetry about Octavian (now the Emperor Augustus). So the poet Horace's life and career rather give the lie to his poetry there.
  7. Innula Zenovka

    The Old Lie: "Dulce et Decorum Est"

    It was part of a project commissioned by the Imperial War Museums, who were presumably content with the way their archives were used. The military historian Stuart Mitchell has some thoughtful criticisms of the way the material was presented: Also, the historian Greg Jenner has a very good thread
  8. Innula Zenovka

    RLV and @setrot

    There's an example of how to use it in Kira Komarov's Quick Collar script in the wiki (the moveTo userfunction): http://wiki.secondlife.com/wiki/Quick_Collar which looks like things I've done with @setrot in the past. The API warns that http://wiki.secondlife.com/wiki/RestrainedLifeAPIKi The wiki example isn't, I think, very helpful, in that it points you in the direction you're already facing, so nothing much is going to happen. The Quick Collar example (which turns the collar wearer to face towards whoever is dragging her) is more practical. You could try looking through the Open Collar scripts and seeing how they do it (that's where I learned it from). If you can't get it to work, I must have a working example somewhere that I've made -- I'll look it out if necessary.
  9. Innula Zenovka

    The Old Lie: "Dulce et Decorum Est"

    I always find the finale to the last Blackadder series strangely moving
  10. Innula Zenovka

    Stealthy RLVa - Who is wearing a permissive relay?

    What's wrong with that, though? If my relay is set to "accept all commands," then things will work as you intend. If my relay is set to "ask," then I get a dialog which I can either accept or decline. Either way things are working as I, the person wearing the relay, want them to.
  11. Innula Zenovka

    Stealthy RLVa - Who is wearing a permissive relay?

    I'm not sure it will. As the Wiki describes it, http://wiki.secondlife.com/wiki/RestrainedLifeAPI So I don't think that's what you're looking for. I agree with KT here -- I think the only way to do it to set a timer when you issue the command and see if you receive a timely acknowledgment from the relay.
  12. Innula Zenovka

    Trying to figure out what the equation is

    It may just be a simple lookup table, something on the lines of integer iXPoints; integer iCounter; integer iMax; integer iCurrentLevel; list lLevels =[ //list of minimum XP points required for each level ]; default { /////// lLevels = llListSort(lLevels,1,TRUE);//make sure the list is in ascending order iMax = llGetListLength(lLevels); iCounter = 0; do { integer n = llList2Integer(lLevels,iCounter); if(iXPoints > n){ iCurrentLevel = iCounter + 1;//assuming levels start at 1 rather than 0 } } while (++iCounter < iMax); llOwnerSay("Your level is "+(string)iCurrentLevel); //////// } Probably you'd want to put the calculation into a userfunction.
  13. Innula Zenovka

    Show linked set

    The timer event looks wrong to me, since I think that the way it's written, as soon as you turn the timer event off, you turn it straight back on again. Since the timer event will continue to fire until you turn it off, there's no need to keep calling llSetTimerEvent in the timer, so I'd simply say timer() { llSetLinkAlpha(count, 1.0,ALL_SIDES); if( ++count == prims) { llSetTimerEvent( 0.0 ); } }
×