Forum Replies Created

Page 5 of 6
  • Uwe Smidt

    Member
    December 19, 2023 at 4:31 pm in reply to: ‘vertical’ Scope of local variables and parameters

    Thank you guys 🙏!

    At least a work around.

    I helped myself with turning the local variables into instance variables. Works but is messy, dangerous & lacking elegance 💃…

  • Uwe Smidt

    Member
    December 19, 2023 at 4:22 pm in reply to: Defining row variables: variable pane vs $definefromsqlclass

    Hi Andreas,

    I’ve enclosed a screenshot of the code editor (but without the error – it comes up only occasionally when debugging on other areas…). The errors come up with lrGP.

    No copying of definitions, but see yourself…:

    Best regards

    Uwe

  • Uwe Smidt

    Member
    December 19, 2023 at 12:33 pm in reply to: DropList in a grid does not scroll on (too) many entries

    Hi Götz,

    I am working on MacOS 14.1.1 (23B81) Sonoma, Omnis 11 xxx5659, and on Safari, Chrome AND Firefox the droplist does not scroll.

    I’ll work around it in the meantime…

    Best regards

    Uwe

  • Uwe Smidt

    Member
    December 1, 2023 at 2:48 pm in reply to: simplifying code…

    Hi Andreas,

    yes, it does help – by knowing FOR SURE it doesn’t work – so I need not over strain my one brain cell ( I only have that one!), and by pointing me in the right direction. I will do a

    taSuper.$getValue(pSchema,pID,pFieldName)

    so I’m not limited to a predetermined field.

    Thanx a lot!

    Uwe

  • Uwe Smidt

    Member
    November 30, 2023 at 2:56 pm in reply to: Export to a file-issues

    issue c) is still unsolved (probably because of this forum software’s tendency to ‘beautify’ paragraphs after ‘preformatted text’ (code blocks etc)):

    How do I kindly ask Omnis to stick to system wide preferences regarding the formatting of numbers, i.e. comma as decimal separator, point as thousands separator?

  • Uwe Smidt

    Member
    November 21, 2023 at 4:54 pm in reply to: $currentlayoutbreakpoint not behaving as expected

    Dear Götz,

    Yep, that worked fine!

    Thank you!

    Uwe

  • Uwe Smidt

    Member
    November 19, 2023 at 4:10 pm in reply to: $currentlayoutbreakpoint not behaving as expected

    Damn… still not working!

    I put

    Do inherited
    Calculate myVariable as $cinst.$currentlayoutbreakpoint
    If $cinst.$currentlayoutbreakpoint=320
    Do $cinst.$objs.native_list.$width.$assign(10)
    Else If $cinst.$currentlayoutbreakpoint=768
    Do $cinst.$objs.native_list.$width.$assign(100)
    Else
    Do $cinst.$objs.native_list.$width.$assign(0)
    End If

    in my remote forms $init, but $cinst.$currentlayoutbreakpoint just doesn’t do anything

    Any ideas?

    Thanks in advance

    Uwe

  • Uwe Smidt

    Member
    November 17, 2023 at 11:21 am in reply to: $currentlayoutbreakpoint not behaving as expected

    Hi Michael,

    This makes perfect sense – thanks for your help!

    Best regards

    Uwe

  • Uwe Smidt

    Member
    November 13, 2023 at 12:54 pm in reply to: Saving named Workspaces

    Dear $Omnis,

    Do you have an update for me? We have Omnis 11 now, and when starting Omnis, there is a message ‘restoring previous IDE state’. So the basic toolkit to fulfill my wishes seems to be there…

    Maybe there is a work around for me in the meantime, like having multiple config files, one for each screen setup…?

    Best regards

    Uwe

  • Uwe Smidt

    Member
    April 20, 2023 at 6:59 pm in reply to: user-defined constants

    Yippiiieeeee!

  • Uwe Smidt

    Member
    December 20, 2023 at 10:01 am in reply to: Defining row variables: variable pane vs $definefromsqlclass

    Good morning Andreas,

    Sorry, the picture was only to show that there were no ‘copydefintions’…, but straight forward code. It is an occasional bug, so I cannot reproduce it right now. My build is newer than the fixed one, so it could be a new/different bug (or old problem sitting in front of the computer)…

    I’ll send you a screenie as soon as the problem reoccurs, but now that the bug knows that YOU are watching it, it will probably hide…

    Have a great week!

    Uwe

    • This reply was modified 2 years ago by  Uwe Smidt.
  • Uwe Smidt

    Member
    November 30, 2023 at 2:50 pm in reply to: Export to a file-issues

    Dear Joey,

    Thank you for your elaborate answer (including a great sample lib!) – so elaborate that it took me a while to evaluate 😉

    But now I did – and yes, you are right, $sendallref does the trick!

    Do ilExportList.$define() ## clear definition
    Do ilExportList.$add()
    # Alter, funktionierender Code ohne $Sendall:
    # For ilColList.$line from 1 to ilColList.$linecount step 1 ## für alle Spalten...
    # If ilColList.export ## NUR die markierten Spalten...
    # Do ilExportList.$cols.$add(ilColList.colname,kCharacter,kSimplechar,255) ## kommen in die Spaltenüberschriften
    # Calculate ilExportList.1.[ilColList.colname] as ilColList.title
    # End If
    # End For
    Do ilColList.$sendall(ilExportList.$cols.$add($sendallref.colname,kCharacter,kSimplechar,255),$ref.export) ## ACHTUNG: hier $sendallref erforderlich, da mit ...$add eine Untermethode mit Parameter aus der Übermethode ...$sendall aufgerufen wird. Nur so wird der Parameter korrekt übergeben (byValue vs byRef)
    Do ilColList.$sendall(ilExportList.1.[$ref.colname].$assign($sendallref.title),$ref.export)

    Because in ilExportList.$cols.$add($sendallref.colname<font face=”inherit”> the $add sends </font>the<font face=”inherit”> parameter into another method, which is why $ref’s by Value does not work, but $sendallref’s by reference does! </font>

    <font face=”inherit”>Thank you for your help in grasping an important difference!</font>

    <font face=”inherit”>Best regards</font>

    <font face=”inherit”>Uwe</font>

  • Uwe Smidt

    Member
    November 29, 2023 at 9:29 am in reply to: Export to a file-issues

    Dear Andreas,
    Thank you for your great sample – I have integrated it into my library, and it works fine!

    Best regards
    Uwe

  • Uwe Smidt

    Member
    November 6, 2023 at 9:49 am in reply to: ERROR: failed to bind Omnis Server Socket

    Great, thanx Andreas!

  • Uwe Smidt

    Member
    November 3, 2023 at 12:19 pm in reply to: ERROR: failed to bind Omnis Server Socket

    Hi Andreas,

    Thank you for your prompt answer!

    So the error message refers to the Node.js port on 6102, and not the Omnis Server port which I put on 5902?

    I’m not using the worker object, but where could I change Node.js port on 6102?

    Thanks a lot & have a great weekend!

    Uwe

Page 5 of 6