[Bricsys] New forum functionality

Hi,

We've updated the forum and added some new features:
  1. New editor: When composing your message, it should be easier to place links and images. Numbered and unnumbered lists are supported as well.
  2. Insert code has been improved. The code preview will automatically resize to the amount of pasted code
  3. Attach files: It's now possible to attach multiple files (of maximum 5 MB) to your post. Viewable attachments (like images) will be displayed at the bottom of your post as thumbnails. When you click on them, the original size will be showed.
  4. Quote functionality: You can quote a previous post into your reply.
I hope you like these new features. If you experience problems, first try to clear your cache and refresh the page (Ctrl + F5). If that doesn't help, contact us here or file a support request.

Bricsys

Comments

  • Quote functionality: You can quote a previous post into your reply.

    That's true. And here is some code
    [code].shareButton{
        float: left;
        margin-right: 10px;
        margin-top: 10px;
        margin-bottom: 10px;
    }[/code]
  • [code]

    bool CGsPreviewCtrl::GetPreviewIcon( AcDbBlockTableRecord::PreviewIcon &preview )

    {

      CDC  *view = NULL;

      HDC   hdcMemDC = NULL;

      HBITMAP  hBmp = NULL;

      bool status = true;

     

      __try

      {

        // Retrieve the handle to a display device context for the client

        view = GetDC();

        if(!view)

        {

          status = false;

          __leave;

        }

     

        HDC   hdcViewDC = view->GetSafeHdc();

        if(!hdcViewDC)

        {

          status = false

          __leave;

        }

     

        // Create a compatible DC which is used in a BitBlt from the View DC

        hdcMemDC  = CreateCompatibleDC(hdcViewDC);

        if(!hdcMemDC)

        {

          status = false;  

          __leave;

        }

     

        int    nWidth  = 32;

        int    nHeight  = 32;

     

        // Create a compatible bitmap from the View DC

        hBmp  = CreateCompatibleBitmap(hdcViewDC, nWidth, nHeight);

        if(!hBmp)

        {

          status = false;  

          __leave;

        }

     

        // Select the compatible bitmap into the compatible memory DC

        HBITMAP  hOld  = (HBITMAP)SelectObject(hdcMemDC, hBmp);

        if(!hOld)

        {

          status = false;  

          __leave;

        }

     

        // Bit block transfer into our compatible memory DC.

        if(!BitBlt(hdcMemDC, 0, 0, nWidth, nHeight, hdcViewDC, 0, 0, SRCCOPY))

        {

          status = false;   

          __leave;

        }

     

        // Get the BITMAP from the HBITMAP

        BITMAP bmp;

        if(!GetObject(hBmp, sizeof(BITMAP),  (LPVOID)&bmp))

        {

          status = false;  

          __leave;

        }

     

        // Calculate the sizes for our memory a 32 x 32 x 8 looks like

        // |...BINFOHDR-40...|....RGBQUAD-1024....|....BMPDATA-1024....|

        WORD  cBitCount = 8;

        DWORD dwBmpSize = ((bmp.bmWidthcBitCount + 31) / 32) * sizeof(RGBQUAD) * bmp.bmHeight;

        DWORD dwSizeofDIB = dwBmpSize + sizeof(BITMAPINFOHEADER);

        DWORD dwSizeofALL = dwSizeofDIB + dwBmpSize;

     

        // alloc all memory

        preview.setLogicalLength(dwSizeofALL);

     

        BITMAPINFO bmpInfo;

        ZeroMemory(&bmpInfo,sizeof(bmpInfo));

     

        // Info for the header

        bmpInfo.bmiHeader.biSize = sizeof(BITMAPINFOHEADER);   

        bmpInfo.bmiHeader.biWidth = bmp.bmWidth;   

        bmpInfo.bmiHeader.biHeight = bmp.bmHeight

        bmpInfo.bmiHeader.biPlanes = 1;

        bmpInfo.bmiHeader.biBitCount = cBitCount;

        bmpInfo.bmiHeader.biCompression = BI_RGB;

     

        // stick the bmpInfo in our array;

        CopyMemory(preview.asArrayPtr(),&bmpInfo,sizeof(BITMAPINFOHEADER));

     

        // Gets the "bits" from the bitmap and copy them into our preview array

        if(!GetDIBits(hdcViewDC, hBmp,0,(UINT)bmp.bmHeight,

                      preview.asArrayPtr()+ dwSizeofDIB, //copy BMPDATA

                      (LPBITMAPINFO)preview.asArrayPtr(),DIB_RGB_COLORS)) // init BITMAPINFO

        { 

          status = false;   

          __leave;

        }

      }

      __finally

      {

        DeleteObject(hBmp);

        ReleaseDC(view);

        DeleteDC(hdcMemDC);

      }

      return status;

    }

    [/code]

  • Nice work!
  • [code]#pragma once
    #include "BrxCoucheManagement.h"
    //-----------------------------------------------------------------------------
    //----- Here you can store the document / database related data.
    class CDocData {

    //----- TODO: here you can add your variables

    public:
    CDocData () ;
    CDocData (const CDocData &data) ;
    ~CDocData () ;

    } ;[/code] 
  • Test...
    With the old editor copy-pasting a piece of html text could lead to (hidden) html formatting being copied a well.
    Copy-pasting some html text: Sander Scheiris
  • Test...
    With the old editor copy-pasting a piece of html text could lead to (hidden) html formatting being copied a well.
    Copy-pasting some html text: Sander Scheiris

    So that problem still persist.
  • ... The Attach files functionality is of course very nice!
  • Testing it too...
    And what is fashion? ;)

    That's true.
  • Test...
    With the old editor copy-pasting a piece of html text could lead to (hidden) html formatting being copied a well.
    Copy-pasting some html text: Sander Scheiris
    Roy,
    For some posts it can be a problem, for other posts it's helpful.
    If you want to avoid this, you will have to "Paste Special" to paste the text with no formatting.

    Best regards,
    Sander
  • #pragma once
    #include "BrxCoucheManagement.h"
    //-----------------------------------------------------------------------------
    //----- Here you can store the document / database related data.
    class CDocData {

    //----- TODO: here you can add your variables

    public:
    CDocData () ;
    CDocData (const CDocData &data) ;
    ~CDocData () ;

    } ;
     

    LPDISPATCH Item(VARIANT Index)
    {
    LPDISPATCH result;
    static BYTE parms[] = VTS_VARIANT ;
    InvokeHelper(0x0, DISPATCH_METHOD, VT_DISPATCH, (void*)&result, parms, &Index);
    return result;
    }

  • I would like to be able to edit my old postings.
    Anything like that in planning?
  • I would like to be able to edit my old postings.
    Anything like that in planning?
    There are no such plans for now.
  • Is it possible to DELETE an attachment while working on a message?
  • Request:
    I would like to see a [Log in] button/feature on each forum page. Now I have to log in via the Meeting Point and then switch back or click on some attachment.
  •  +1 for log in button.  I am not a fan of the meeting point.  I am sure it fits into the workflow and mindset of a lot of people but trying to fit answers into a set number of characters really irks me :)  Also having to scroll up and down to find the initial message in a thread isn't very fun either.  Just my 2 cents. 
  • Hi,
    We will implement a logon button somewhere Q1 2012.
    Sander
  • Hi,
    We will implement a logon button somewhere Q1 2012.
    Sander
    Great, thank you.
  • TEST... TEST
    The forum software doesn't 'like' pointy brackets:
    Let's see if this works: < >

  • ... To get correct pointy brackets:
    For < (less than) use: &lt;
    For > (greater than) use: &gt;
  • Of course pointy brackets are also used in Lisp code.
    Test Example:
    [code](setq ss
      (ssget
        (list '(-4 . "          '(0 . "LINE")
              '(0 . "LWPOLYLINE")
              '(0 . "POLYLINE")
              '(0 . "ARC")
              '(-4 . "OR>")
        )
      )
    )
    [/code]
  • In my previous post the display of the first -4 gc is incorrect. It seems wise to always (also) attach your Lisp code.

    Another test example:
    [code](setq ss (ssget (list '(-4 . ""))))[/code]
  • ... To get correct pointy brackets:
    For < (less than) use: <
    For > (greater than) use: >

    Yes, that could cause some "problems"... A disappearing act most likely.
    Some HTML of the posts get parsed/filtered out etc
    Maybe we can try to find a way to recognize it better in a next iteration.
This discussion has been closed.