Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

  • Isomorphic
    replied
    We plan to address the reload of the skin as well, but it's not high priority as it doesn't appear to be actually breaking anything in the Feature Explorer.

    Leave a comment:


  • Isomorphic
    replied
    Thanks, we're looking into those logs already - probably just a demotion of log level, given that the items in question are ButtonItems which don't have a sensible use for operators.
    Last edited by Isomorphic; 30 Aug 2018, 00:17.

    Leave a comment:


  • Blama
    replied
    Hi Isomorphic,

    I can see the exception is gone, the sample from #2 does still display this though (v12.0p_2018-08-25):

    Code:
    *15:35:43.960:XRP6:WARN:ButtonItem:isc_ButtonItem_0[filterButton]:Detected defaultOperator, 'iContains', is unsupported in this item.  Valid operators are: [
    "equals",
    "notEqual",
    "lessThan",
    "greaterThan",
    "lessOrEqual",
    "greaterOrEqual",
    "between",
    "betweenInclusive",
    "isBlank",
    "notBlank",
    "isNull",
    "notNull",
    "equalsField",
    "notEqualField",
    "greaterThanField",
    "lessThanField",
    "greaterOrEqualField",
    "lessOrEqualField",
    "and",
    "or",
    "not"
    ]
     Using equals instead.
    *15:35:43.972:XRP6:WARN:ButtonItem:isc_ButtonItem_0[filterButton]:Detected defaultOperator, 'iContains', is unsupported in this item.  Valid operators are: [
    "equals",
    "notEqual",
    "lessThan",
    "greaterThan",
    "lessOrEqual",
    "greaterOrEqual",
    "between",
    "betweenInclusive",
    "isBlank",
    "notBlank",
    "isNull",
    "notNull",
    "equalsField",
    "notEqualField",
    "greaterThanField",
    "lessThanField",
    "greaterOrEqualField",
    "lessOrEqualField",
    "and",
    "or",
    "not"
    ]
     Using equals instead.
    Best regards
    Blama

    Leave a comment:


  • Isomorphic
    replied
    We fixed the validOperators issue, you can retest in builds dated August 25 and later

    Leave a comment:


  • Blama
    replied
    Both issue also happen here on hover of the column header of "Item name".

    Leave a comment:


  • 11.1p / 12.0p sample warning w.r.t to twice loaded skin (?!) and exception for getValidOperators on ListGrid column header hover

    Hi Isomorphic,

    please see this sample in 11.1 / 12.0p:

    Developer console entry on start:
    Code:
    15:41:31.015:MUP4:WARN:Log:New Class ID: 'IAutoFitButton' collides with ID of existing Class object '[Class IAutoFitButton]'.  Existing object will be replaced.
    15:41:31.015:MUP4:WARN:Log:New Class ID: 'HeaderMenuButton' collides with ID of existing Class object '[Class HeaderMenuButton]'.  Existing object will be replaced.
    15:41:31.017:MUP4:WARN:Log:Detected loading of more than one skin - 'Tahoe' was loaded when 'Tahoe' was already loaded.  See the QuickStart Guide for instructions on correctly changing the current skin
    Also, on hover of the column header of "Item name", I get this exception (12.0p only!):
    Code:
    15:42:28.821:MMV6:WARN:Log:TypeError: Cannot read property 'getValidOperators' of null
    Stack from error.stack:
        ListGrid.getFieldUIOperatorList(<no args: exited>) on[ListGrid ID:orderItemList] @ ISC_Grids.js:1842:592
        ListGrid.getFilterOperatorMenuItems(<no args: exited>) on[ListGrid ID:orderItemList] @ ISC_Grids.js:2774:311
        ListGrid.getHeaderContextMenuItems(<no args: exited>) on[ListGrid ID:orderItemList] @ ISC_Grids.js:2797:266
        ListGrid.shouldShowHeaderMenuButton(<no args: exited>) on[ListGrid ID:orderItemList] @ ISC_Grids.js:2652:90
        _3.handleMouseOver(<no args: exited>) on [Button ID:isc_Button_4] @ ISC_Grids.js:2553:180
        [c]EventHandler.bubbleEvent(<no args: exited>) on [Class EventHandler] @ ISC_Core.js:2134:89
        [c]EventHandler.handleEvent(<no args: exited>) on [Class EventHandler] @ ISC_Core.js:1856:351
        EventHandler.__handleMouseMove(<no args: exited>) on [Class EventHandler] @ ISC_Core.js:1941:19
        EventHandler._handleMouseMove(<no args: exited>) on [Class EventHandler] @ ISC_Core.js:1925:244
        [c]EventHandler.handleMouseMove(<no args: exited>) on [Class EventHandler] @ ISC_Core.js:1925:11
        [c]EventHandler.dispatch(_1=>[c]EventHandler.handleMouseMove(), _2=>[object MouseEvent]) on [Class EventHandler] @ ISC_Core.js:2221:108
        HTMLDocument.eval(event=>[object MouseEvent]) @ [no file]:3:123
    This is most likely the same as this issue.

    Best regards
    Blama
Working...
X